A new service page has been published, but it has not appeared in search yet. Before requesting indexing, check that the finished page is available at its final URL, with no password, placeholder page, or accidental indexing block.
Start by viewing the page without logging in to the content management system (CMS). Read the offer as a potential customer: is it clear what service you provide, who it is for, what the customer will receive, and how to get in touch? Then check the technical requirements. A successful server response does not replace useful content.
Make sure the correct version is published
Open the final URL in a private browser window. Compare the heading, main text, contact details, and form with the prepared version. If the old text is visible when you are logged out, check the publication status and cache.
Submit a test inquiry through the form and confirm that it arrives through the working channel. This is a separate check: a page with a working button does not prove that inquiries are being delivered. Do not enter real customer data in a public test.
If the main text appears through JavaScript, wait for it to load and check for errors. Do not assume that all JavaScript interferes with search: check whether the search engine can access the content of this specific page.
Check the response and indexing blocks
A developer can save the headers and HTML with a separate GET request:
curl -sS -D headers.txt -o page.html \
https://example.com/services/installation/Check the HTTP status in headers.txt. If the URL redirects, check the destination page and use its URL for further actions. Look for X-Robots-Tag in the headers, and meta name="robots" and the canonical in the HTML.
The published page should not accidentally retain noindex from the test template. Also check robots.txt for the relevant domain: is crawling of this path allowed? Do not remove protection from the entire test site just to publish one service page. The differences between these restrictions are explained in this comparison of robots.txt, meta robots, and X-Robots-Tag.
Clarify how the page differs from nearby services
If this is a standalone service, its canonical should not accidentally point to an older general page. First determine the correct primary URL, then configure it using the canonical guide.
Check the title—the page name shown in the browser tab—and the H1, its main visible heading. They should clearly name the service. Remove any leftover references in the template to another service, a test city, or an unverified price. If the price depends on the scope of work, explain how you calculate it and what information is needed for an estimate.
For example, a page titled “Ventilation installation for cafes” is more useful when it describes the scope of work, the required source information, the approval process, and the conditions for an on-site visit. These details must reflect the company’s actual work. Rearranging the words on a general page does not explain the new service to visitors.
Add a path to the page from the site
Add a regular link from a relevant services section. Check its address in the href attribute and open the link in a browser. If people can reach the page only through a URL sent to them, it will be harder for visitors and search crawlers to find it.
Add the final indexable URL to the sitemap, if the site uses one. The modification date should reflect a real update, not change daily without a reason. Make sure the sitemap no longer lists a test URL or a URL that redirects.
Request crawling after making fixes
In Search Console, check the URL and the current page. If the technical barriers have been removed, you can request indexing. Google describes this process; a request does not guarantee that the page will appear in search or specify a timeframe.
Record the publication date and the check results. When you next review Search Console, compare the last crawl date: the previous message may have referred to the version from before the fix. Do not change the URL every time the result does not appear immediately.
Before putting the page into operation, run a technical audit. Record four results: the finished text is available to visitors who are not logged in, indexing blocks have been checked, internal links point to the final URL, and the search crawler can access the current version.