Blog

A WordPress page can look perfect on your website and still be invisible on Google. Usually, the first job is figuring out whether Google cannot access the page, has chosen not to index it, or has indexed it but ranks it too low for you to find.

Those are different problems, and they need different fixes. Before installing another SEO plugin or rewriting every page, use the checks below to narrow down what is actually happening.

First, separate indexing from ranking

Google generally needs to discover a URL, crawl its content, and decide whether to include it in its index before that page can appear as a normal search result. Being indexed makes a page eligible to appear, but it does not guarantee visibility for your preferred keywords.

• Discovery problem: Google does not know the page exists.
• Crawling problem: Google knows the URL but cannot reliably access its content.
• Indexing problem: Google has encountered the page but has not included it in its index, or has selected another URL instead.
• Ranking problem: The page is indexed, but other pages appear ahead of it for the searches you care about.

A search using site:yourdomain.ca can provide a quick clue, but it is not a complete list of indexed pages. Do not use missing results from that search alone as proof that Google has ignored your website.

1. Inspect the exact page in Google Search Console

Google Search Console is the best starting point because it reports what Google knows about a specific URL. If you have not connected your website yet, see How to Set Up Google Search Console for Your WordPress Website.

Use URL Inspection to check the full address of the missing page. Include the correct HTTPS address and the correct www or non-www hostname, rather than assuming every variation behaves the same way.

Record these details before making changes:

• Whether the URL is indexed.
• The reported reason if it is not indexed.
• Whether crawling and indexing are allowed.
• The last crawl date, if one is available.
• The Google-selected canonical URL, where reported.
• Any page-fetch or server errors.

The indexed report reflects Google's stored information, which may predate your latest changes. Use the live test to check current accessibility, but remember that a successful live test does not guarantee indexing or rankings.

Pick one important missing page and diagnose it fully before changing the whole site. A single-page issue may be a page setting; the same issue across every service page may point to a shared template, plugin setting, or server rule.

2. Check WordPress search visibility and page settings

Look for the site-wide search engine setting

In WordPress, go to Settings > Reading and look for “Discourage search engines from indexing this site.” On a public business website that you want indexed, this should normally be unchecked.

This setting is sometimes left enabled after development or a redesign. Unchecking it removes that particular discouragement, but other plugins or hosting settings can still block indexing.

Do not disable it indiscriminately on staging or development sites. Those copies should remain out of search, preferably with access protection rather than relying only on a search engine directive.

Check whether the page itself is public

Confirm that the missing page is published and publicly accessible. Drafts, private pages, password-protected content, and pages behind a membership login are not suitable public search landing pages.

Open the URL in a private browser window while logged out of WordPress. If you see a login form, a maintenance screen, or different content from what you see as an administrator, investigate that before adjusting SEO settings.

Check the page's SEO controls

SEO plugins such as Yoast SEO, Rank Math, and All in One SEO can apply indexing rules to individual pages or entire content types. Look for a setting that prevents the page from appearing in search results, often described as noindex.

Check both the individual page and the global settings for Pages, Posts, or any custom content type involved. Labels vary by plugin, so consult the plugin's official documentation for current instructions rather than installing a second SEO plugin to override the first.

3. Understand the difference between robots.txt and noindex

These controls are frequently confused. A robots.txt rule controls crawling, while a noindex directive tells a supporting search engine not to include content in its index.

If your public service page is blocked by a broad crawling rule, Google may be unable to read its content. Review the site's robots.txt output for rules affecting that URL, especially after a launch or migration.

A developer can also check for noindex in the page's robots meta tag and in an X-Robots-Tag HTTP response header. The header matters because an indexing restriction can come from the server or hosting configuration, not just WordPress.

• Remove unintended crawling restrictions from pages you want Google to access.
• Remove unintended noindex directives from public pages you want indexed.
• If you want Google to process a noindex directive, allow it to crawl the page.
• Keep private content protected with authentication or appropriate access controls.

Do not replace your entire robots.txt file with a snippet from a random tutorial. Existing rules may serve a purpose, and allowing crawling everywhere can expose unnecessary URLs without improving visibility.

4. Make sure the page returns the right response

A page intended for indexing should normally return an HTTP 200 response with meaningful content. A page that redirects, returns an error, or displays an error message despite returning 200 needs a different diagnosis.

Server errors and blocked requests

Repeated 500 or 503 errors can interfere with crawling. A 403 response or a security challenge may mean your firewall, security plugin, or CDN is blocking access.

If URL Inspection reports a fetch problem, ask your host or developer to review the relevant logs. Do not disable the entire firewall just to see whether Google can get through, and do not trust a claimed Googlebot user-agent alone as proof that a request is genuine.

Missing pages and soft 404s

A genuine 404 response is appropriate for a page that no longer exists and has no suitable replacement. For a page that should exist, restore its content or correct the broken URL.

A “soft 404” means Google thinks the page resembles an error or empty page even though the server may report success. An empty product page or a template displaying “content unavailable” can create this problem.

Redirects after a redesign

If an old URL redirects to a replacement page, Google will generally work towards indexing the destination rather than keeping the old address as a separate result. Inspect the destination URL before assuming the redirect is an indexing failure.

Check that redirects lead to genuinely relevant replacements rather than sending every missing page to the homepage. For a planned URL change, see How to Redirect Old WordPress URLs Without Losing SEO After a Redesign.

5. Check which URL Google considers the main version

WordPress can expose similar content through multiple addresses, including tracking parameters, category archives, and alternate domain variations. A canonical tag suggests which URL should be treated as the main version.

For a unique public service page, the canonical will usually point to that page's preferred URL. If it accidentally points to the homepage, a staging domain, or an unrelated service page, Google may choose not to index the intended URL separately.

Compare the user-declared canonical with the Google-selected canonical in URL Inspection where available. Google treats canonical declarations as signals, not commands, and can select another URL when other evidence conflicts.

• Use the preferred URL in your internal links.
• Include that same preferred URL in the XML sitemap.
• Avoid declaring a redirected or missing URL as canonical.
• Use consistent HTTPS and hostname settings.

Do not force every URL to be indexed separately. Duplicate print views, tracking URLs, and similar variations generally do not need their own search listings.

6. Help Google discover important pages

Check the XML sitemap

An XML sitemap helps Google discover the URLs you consider useful. WordPress core or an SEO plugin may generate it, so check your actual configuration rather than assuming a particular sitemap address.

In Search Console, confirm that your submitted sitemap can be fetched and that the missing page appears in the appropriate sitemap. It should normally list the final, canonical, indexable URL, not a redirect, private page, or broken address.

A sitemap is a discovery aid, not an indexing guarantee. Submitting the same unchanged sitemap repeatedly will not resolve a noindex directive or improve thin content.

Add useful internal links

A page with no incoming links from elsewhere on your site can be difficult to discover and easy to overlook. Link important service pages from relevant navigation, service summaries, or related articles using ordinary crawlable links.

Use descriptive wording, such as “commercial electrical services,” rather than adding a collection of vague “click here” links. The link should help a visitor find something useful, not exist solely for a search engine.

7. Interpret “discovered” and “crawled” exclusions carefully

Discovered, currently not indexed

This generally means Google knows the URL but has not yet crawled it. Check internal links, sitemap inclusion, and server reliability before assuming the page needs a rewrite.

On sites that generate large numbers of filter, tag, or parameter URLs, Google may spend time discovering low-value variations. A developer can review that URL structure without removing useful customer navigation indiscriminately.

Crawled, currently not indexed

This means Google crawled the page but has not included it in the index at that point. It is not a diagnosis of a specific content problem, and repeatedly requesting indexing is not a reliable fix.

Review whether the page offers something distinct, whether it substantially duplicates another page, and whether Google could see its main content. Use Search Console's available rendered-page information to investigate content that depends heavily on JavaScript.

For example, several location pages that only swap a city name may offer little reason to index each one. A useful local page can explain actual service coverage, relevant work, and location-specific information, provided those details are true.

For practical help improving the content itself, see How to Write Content for Your Business Website.

8. Check security issues and manual actions

If pages disappeared suddenly, review Search Console's Security Issues and Manual Actions reports. These require a different response from ordinary discovery delays or duplicate-page exclusions.

Unexpected spam content, unfamiliar redirects, or search snippets advertising products you do not sell can point to a compromised site. Fixing the visible page alone may leave the underlying infection in place.

Ambrite provides WordPress hack cleanup and recovery, including Google review request handling after cleanup when Google has flagged the site. A review request does not guarantee a particular recovery date or search position.

9. If the page is indexed, investigate ranking instead

When URL Inspection confirms that the intended page is indexed, stop treating the issue as a missing-index problem. Open Search Console's Performance report and filter by that page to see whether it receives impressions and which queries trigger them.

Low visibility can reflect strong competition, limited relevance to the query, or content that does not answer the searcher's question. A page titled “Services” with two generic sentences gives Google and potential customers less useful information than a clear explanation of the actual service.

For a Canadian local business, check whether the page accurately states the service offered and the area served. A .ca domain can support a Canadian identity, but it does not override indexing restrictions or guarantee local rankings.

Slow performance is worth addressing, especially when timeouts prevent crawling. However, a better speed score alone will not remove a noindex directive or make an irrelevant page competitive.

After fixing the problem, verify before requesting indexing

1. Open the page while logged out and confirm that the correct public content appears.
2. Check that it returns the intended response and no longer carries accidental indexing restrictions.
3. Confirm that its canonical, sitemap entry, and internal links agree on the preferred URL.
4. Clear relevant page and CDN caches if they still serve old settings or content.
5. Run a live URL Inspection test, then request indexing if the page is eligible and the option is available.
6. Record what changed and monitor Search Console for a later crawl and updated status.

Google may take days or weeks to revisit and reassess a page, sometimes longer. There is no guaranteed indexing deadline, and repeatedly clicking “Request indexing” does not make the process immediate.

When to get help instead of changing more settings

Bring in a developer when the live test and browser show different results, many pages disappear together, or canonical and indexing settings keep changing back. Those patterns can involve a shared template, server configuration, caching layer, or plugin conflict.

Ambrite's WordPress maintenance plans cover technical upkeep such as updates, backups, monitoring, and included time for small fixes. Maintenance is not a promise of Google indexing or SEO results.

If you need help investigating, contact Ambrite by email or open a support ticket if you are an existing client. Include the affected URLs, the exact Search Console message, when you first noticed the issue, and any recent redesign, hosting, or plugin changes so the developer has something concrete to work from.

This article was written with the help of AI and reviewed by Ambrite. Pricing, features, and technical details may change, so always verify with official sources before making decisions.