All articles
Guides5 min read

Check search visibility after your WordPress website launches

Check WordPress visibility settings, public pages and Google’s inspection reports after launch. A practical review for Tempe business owners.

Your new website opens on your phone. The contact page works. But an important service page is missing when you look for it on Google.

Before rewriting the page, check whether the launched site still carries an instruction intended for its development copy. A page can be available to customers while asking search engines to leave it out.

For a Tempe business using WordPress, this is a useful launch review to complete with the person maintaining the site. It checks a specific possible obstacle; it does not promise a search position.

Choose the pages that should be public

Start with the actual website address customers use. Include the homepage and a small group of important service or product pages. Copy their complete addresses into a shared note.

Keep the development copy separate. A preview address, an unfinished campaign and a private customer area may have different visibility requirements. Do not remove restrictions from everything simply because the main website is ready.

Imagine a Tempe repair business launching a new appliance-service page. The public service description should be available for discovery. A private estimate prepared for one customer has a different purpose.

An imagined repair-business launch
Public service page
Finished service details for customers to discover.
Development copy
A separate working version, with its own restrictions.
Customer estimate
Private information requiring access controls.

Open each intended public page in a signed-out browser. Confirm that it shows the finished content without a login or maintenance screen. Save the final address if the browser takes you somewhere else.

If the launch changed page addresses, use our URL-change guide for the separate redirect review. Inspect the destination you intend customers to reach.

Review the WordPress visibility setting

Ask your maintainer to open Settings, then Reading, on the production WordPress site. Confirm the website address before making a change.

WordPress has a “Discourage search engines from indexing this site” option. When checked, it asks search engines not to index the site. It does not block ordinary visitors. Read WordPress’s Reading settings documentation.

For a site intended to be discoverable, ask whether that option was left checked during launch. If it was accidental, clear it and save the change. Record who changed it and when.

Do not use this option as protection for private information. Our preview-page guide explains why a review link needs a deliberate access arrangement.

Brandon reviewing a website at his desk in the Juncie studio
Review the setting and the published page together. Brandon in the Juncie studio; photo from the Juncie studio archive.

A screenshot of the saved setting is a useful starting point. The next check is what the public website actually sends.

Check the instruction on the live page

Have your maintainer inspect the affected page’s published HTML and response headers. Ask whether either includes an unintended noindex rule, and where it comes from.

Google supports noindex in a page’s metadata or an HTTP response header. When Google crawls an accessible page and reads that rule, it excludes the page from its search results. See Google’s noindex documentation.

You do not need to edit code yourself. Ask for a plain result: the exact page checked, the restriction found, its source and the intended correction. A plugin setting or server configuration may need attention even after the WordPress checkbox is cleared.

Have the maintainer check the public response again after the correction. If a cached copy still supplies the old instruction, resolve that and repeat the check. Then inspect another page using the same template.

Avoid copying a robots.txt change from a forum without a diagnosis. Google must be able to crawl a page to see its noindex rule; a robots.txt block can prevent that. The two controls do different jobs. Read Google’s explanation of this interaction.

Compare the live page with Google’s record

Ask someone with access to your site’s Search Console property to inspect the exact public URL. Keep the result with your launch note rather than relying on a general search for the business name.

URL Inspection shows information about Google’s indexed version. Its live test checks the current page. A successful live test does not guarantee that Google will index the page or show it in search results. Review Google’s URL Inspection guidance.

Keep these checks separate
Your browser

Can a signed-out visitor open the finished page?

The live response

What search instructions does the website send now?

Google’s record

What does URL Inspection report about the indexed version?

Read the reported reason when a page is not indexed. If it identifies an exclusion you intended, leave it in place. If it points to an unintended restriction, ask the maintainer to fix that cause.

For the imagined repair business, keep the new service page’s result separate from the homepage’s result. One successful check does not establish that every page on the site behaves the same way.

A different reported problem needs its own diagnosis. Do not repeatedly change visibility settings when the evidence points somewhere else.

Request another review after the fix

Once the public page has been corrected, the authorized site manager can use URL Inspection to request indexing. Keep the request date beside the verified change.

Google says recrawling can take days to weeks. A request does not guarantee inclusion, and repeated requests for the same URL do not make it happen faster. Read Google’s recrawl guidance.

Agree on a follow-up date and an owner. At that review, compare the current page, Google’s reported status and the last change. This gives your maintainer a useful sequence of evidence if the problem remains.

Do not keep changing a correct page while waiting for a new crawl. If the report identifies another issue, investigate it deliberately and record the next change separately.

Search descriptions are another task. Our description guide covers introducing a page accurately in search, including why the wording Google displays may differ.

Keep visibility in the launch handover

Add this review to the handover for a rebuild, migration or replacement of a development site. Name the production address, the pages checked and the person responsible for follow-up.

Keep private previews and customer material on a separate list with their intended access controls. That makes it harder for a broad launch change to expose something that should remain restricted.

Repeat the affected checks when a maintainer changes the SEO setup or replaces a site with a staging copy. The useful evidence is the live result, not a remembered checkbox from an earlier launch.

Treat a corrected restriction as a completed repair. It is not evidence of higher rankings or more enquiries on its own.

Launching or rebuilding your Tempe business website? Our technical SEO service can help check the public pages and their search instructions. Show Brandon the page you want to investigate.

A little more clarity

Common questions.

Ask a different question
Does a page opening in my browser mean Google can index it?
No. A public page can still carry a noindex instruction. Ask your maintainer to check the published page and its response headers, then review the exact URL in Search Console.
Does the WordPress search visibility setting protect private content?
No. It asks search engines not to index the site but does not prevent people from opening it. Keep private content behind appropriate access controls.
Will removing an accidental noindex rule put us first in Google?
No. Correcting an unintended restriction removes that particular obstacle. It does not guarantee indexing, a ranking position or more enquiries.
JUNCIE STUDIOS

Your website could be
working harder for you.

Tell me what’s getting in the way. I’ll help you figure out the next step for your business.

Talk to me about your website
Brandon Mitchell
Brandon MitchellDesigner, developer & your point of contact.Based in Arizona. Built around your business.