How to Check That WordPress Is Indexed Correctly

check wordpress indexing

Quickly identify whether your pages are being picked up by Google

If your WordPress site does not appear (or appears little) on Google, the issue is not always SEO in the broad sense: it can simply be an indexing problem. Before optimizing content, you must make sure Google can discover your pages, crawl them, and add them to its index (indexing). The goal here is to methodically check whether important pages are indexed, whether some are excluded, and why.

Start with the essentials: list your priority URLs (homepage, categories, service pages, pillar articles, local pages…). Then check whether they actually appear in Google. The simplest method is to run site: searches (e.g. site:yourdomain.tld) and also test specific URLs. This approach gives a first indicator, but it can be imprecise (Google does not always show all indexed URLs via site:). For reliable checking, you should then use Google Search Console and cross-check signals.

Check indexing with Google Search Console (most reliable method)

Google Search Console (GSC) is the reference tool for seeing how Google views your site. It lets you check the indexing status of a specific URL, understand reasons for exclusion, and monitor the number of indexed pages over time.

1) Use URL Inspection for a specific page

In GSC, the URL Inspection tool tells you whether a page is:

– Indexed (and in which version: canonical chosen by Google or declared by you)
– Crawled recently or not
– Blocked (robots.txt, noindex, redirect, 404, soft 404…)
– With retrieval issues (server errors, response time, etc.)

For each critical page, run the inspection: if it is not indexed, the tool will often give you a clear reason. Once the issue is fixed (e.g. removal of an inadvertent noindex), you can request indexing.

2) Review the Pages report (overall indexing)

The Pages report (formerly Coverage) classifies URLs into several categories: indexed, excluded, with warnings, and errored. The key point is to identify patterns affecting pages you want to appear in Google:

– Excluded by ‘noindex’ tag: the page explicitly tells Google not to index it.
– Redirected page: normal if the URL redirects, but watch out for an unintended redirect that prevents reaching the final page.
– Crawled currently not indexed: Google has seen the page but chooses not to add it (often quality/perception, duplication, low value).
– Discovered – currently not indexed: Google knows the URL but is not crawling it (often crawl budget, weak internal linking, sitemap overload, server performance).

The best practice is to sort by volume and importance: some exclusions are normal (filter pages, useless tags, internal search results), but others are warning signs if they affect your business pages.

3) Validate submitted sitemaps

In GSC, check the Sitemaps section: a submitted sitemap marked Success does not imply everything is indexed, but it indicates Google received a list of URLs. If the sitemap shows errors (format, inaccessible URLs, 404 pages, blocked URLs), fix them before requesting another crawl. In WordPress, an SEO plugin or the native sitemap may be sufficient, but quality matters: a clean, coherent, up-to-date sitemap is better than a large sitemap with many useless URLs.

Perform a site diagnosis: and targeted queries (useful, but to be interpreted)

Google queries like site:yourdomain.tld are an excellent quick check. To refine:

– Test site:yourdomain.tld\/page-to-check (or part of the URL).
– Test site:yourdomain.tld "exact title" to find a page via its title.
– Compare results between HTTP/HTTPS and www/non-www if your historical configuration has changed.

Warning: if pages appear with odd titles, spammy descriptions, or URLs you don't recognize, this may indicate a security issue, injected content, or indexing of unwanted URLs (parameters, search pages, etc.).

Check WordPress settings that block (or degrade) indexing

A site can be technically online but prevent indexing via simple settings. Here are the essential WordPress checks.

1) The option Ask search engines not to index this site

In WordPress, the search engine visibility option can be checked by mistake (often in preproduction, then forgotten when moving to production). If active, WordPress adds a directive discouraging indexing. Check this first, especially after a launch or redesign.

2) The meta robots tags (noindex, nofollow) at the page/taxonomy level

SEO plugins allow setting noindex for certain sections: categories, tags, author archives, internal search results pages, etc. A common mistake is setting strategic pages to noindex (e-commerce categories, service pages, local pages). Audit this: what should be indexed must not be noindexed.

3) The robots.txt file (unintentional blocks)

An overly restrictive robots.txt can prevent Google from crawling crucial directories (images, JS/CSS, plugin folders, etc.). If Google cannot load certain files, it may misinterpret your pages' rendering. Also check that no rule is abusively blocking /wp-content/ or that important URL parameters are not disallowed without reason.

4) Canonicals and duplication

The canonical indicates the reference URL for content. If it points to the wrong page, you can unintentionally deindex pages (Google often follows the canonical). This happens after:

– a migration (URL, domain, or protocol changes)
– similar/duplicated pages (variations, parameters, printable pages)
– SEO plugin settings applied incorrectly

Understanding common causes of exclusion in Google (and what to do)

When GSC reports exclusions, the goal is not to index everything, but to index what matters. Here are the most frequent cases on WordPress.

Page Crawled – currently not indexed

This is often the most frustrating case: Google crawled but does not index. Likely causes:

– content too thin or too similar to other pages on the site
– low perceived value (generated pages, empty tags, pointless archives)
– insufficient internal linking (the page is isolated)

Actions: enrich the page, strengthen internal linking (links from menus, pillar pages, categories), improve semantic context (titles, structure), and limit creation of poor pages (automatic tags, useless author pages).

Discovery Page currently not indexed

Here, Google knows the URL but does not crawl it. Likely causes:

– too many submitted URLs (bloated sitemap), and Google prioritizes
– high server performance/TTFB, instability, occasional 5xx errors
– high click depth (page too far from the homepage)

Actions: lighten the sitemap, improve performance, increase the internal visibility of important pages, and avoid producing too many low-value URLs.

Soft 404, 404 and errors after redesign/migration

Deleted pages without redirection, changed permalinks, or a structural change can generate many 404s. This affects crawling (Google wastes time), user experience, and the consolidation of SEO signals.

If you have just finished a migration or redesign, address errors quickly. A dedicated guide can help you handle this properly: Fixing 404 Errors After a Migration.

Redirections and redirect chains

Redirects are normal (HTTP→HTTPS, www→non-www, old URLs→new), but chains (A→B→C) and loops harm crawling. Simplify: a single redirect to the final destination, preferably a 301, and avoid plugins that add conflicting rules.

Analyze internal linking: indexing also depends on discoverability

Google crawls a site by following links. On WordPress, a page's indexing depends heavily on its place in the internal linking:

– A page accessible from the menu, a category, and multiple posts is more likely to be crawled regularly.
– A published but unlinked (orphan) page can remain discovered but sparsely crawled.
– Pages that are too deep (4–5 clicks) may be crawled rarely.

Best practices:

– link each important page from at least one strong page (homepage, categories, pillar pages)
– use relevant related-articles blocks
– check that category pages are not dead ends (add text, links, subcategories)

Monitor server performance and technical signals that slow down crawling

A slow or unstable WordPress can reduce crawling. Even without a penalty, Google adapts its crawl rate to the server’s capacity. Indicators to watch:

– spikes of 5xx errors in GSC
– high response time (TTFB)
– pages that take a long time to load or that timeout

Common actions: server cache and page cache, image optimization, reducing heavy plugins, updating PHP, maintained database, CDN if necessary. The idea is not to optimize everything, but to remove bottlenecks that prevent Google from crawling properly.

Prevent security issues from sabotaging your indexing

A compromised site can generate spam pages, inject links, or modify templates to show different content to bots. Consequences: indexing of unwanted URLs, hacked content alerts, drop in visibility, or even partial deindexing.

To prevent the most common causes, you can review the typical errors that make WordPress vulnerable: The Most Common Security Errors.

If you already suspect a compromise (unknown pages indexed, strange redirections, unrecognized admin), you must act immediately with a cleanup plan: Hacked Cleanup and Hardening Steps.

Finally, reducing the attack surface indirectly helps indexing (more stable site, less spam). One simple lever is to harden admin access: How to Limit Login Attempts on.

Special case: managing indexing across multiple WordPress sites

When you manage a fleet of sites (multi-brand, franchises, local sites, legitimate PBN, client projects), indexing problems become recurrent: inconsistent sitemaps, disparate configurations, inter-site duplication, repeated migrations. The solution is to industrialize checks:

– configuration model (SEO plugin, robots, sitemaps, structure)
– launch checklist (GSC, analytics, indexing, redirects)
– monitoring GSC errors and server logs
– publishing process (avoid proliferation of low-value pages)

To structure this management, this guide is useful: How to Manage a Portfolio of Sites Effectively.

Tools and resources useful to confirm your indexing status

Beyond GSC, some resources explain complementary methods and concrete points of caution. For example, you can compare different ways to check indexing status and interpret signals: How to Check Your Google Index Status in WordPress.

If your priority is to trigger cleaner indexing after a launch or redesign, a step-by-step approach can help ensure nothing is forgotten: How to Index Your WordPress Site | Practical Guide 2026.

To dig deeper into visibility checks and the signals that show a site is truly being taken into account by Google (and not just accessible), you can consult: A site visible and well indexed by Google. How to do it.

Finally, if you’re looking for an overview of actions to take on the WordPress and Google sides to facilitate indexing, this resource can complement your checklist: WordPress and Google: how to index your website.

30-minute action plan: check and fix the essentials

If you need to move quickly, follow this order:

1) Check 5 critical URLs via the URL Inspection in GSC (homepage + 4 business pages).
2) Open the Pages report: spot errors and exclusions related to these URLs (or their families).
3) Check the WordPress visibility setting and the absence of noindex on your strategic pages.
4) Check the robots.txt to avoid an inadvertent blockage.
5) Check redirects/404s (especially after migration).
6) Strengthen internal linking to important but non-indexed pages.
7) If the site is slow or unstable: prioritize server stability and caching.

When to delegate: ongoing maintenance and monitoring

Indexing is not a one-shot setting. With each plugin addition, theme change, redesign, migration, or structural modification, issues can occur: accidental noindex, bloated sitemaps, 404 errors, redirect chains, degraded performance. Implementing regular maintenance (updates, GSC checks, error monitoring, security, performance) prevents indexing problems from taking hold.

If you want to secure these checks over time, you can discover our maintenance offers for WordPress sites.

You may also be interested in these articles:

Optimizing WordPress after a redesign Why Your WordPress Site Is Slow (Even with Few Plugins) Fix the WordPress Database Connection Error Why an Unmaintained WordPress Site Loses Search Rankings