Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.

To get a WordPress page considered for Google Search, make sure it is publicly accessible and not blocked from indexing, submit your site’s sitemap in Google Search Console, and inspect key URLs. These steps help Google discover and evaluate your pages; they do not guarantee that Google will crawl or list them.

1. Make sure Google can reach your site

A page behind a login, blocked by network rules, or returning a server error cannot be fetched normally for crawling. Open the page in a private browser window to check that it is public, then resolve any access or availability problem. Google’s SEO guide for web developers recommends using URL Inspection to check how Google accesses and renders a page.

If Google cannot fetch a page, check the server response, DNS or firewall restrictions, and any unintended crawl block in robots.txt. URL Inspection can help distinguish an access problem from an indexing issue.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

2. Check robots.txt and noindex

These controls do different things. robots.txt controls whether crawlers can access URLs; a noindex directive tells a crawler that can access a page not to show it in search. Google must be able to crawl a page to read its noindex directive, so blocking a page in robots.txt is not a substitute for noindex.

  • If a page should be eligible to appear in search, remove any unintended robots.txt block and noindex directive.
  • If an accessible page should stay out of search, use noindex and allow Google to crawl it so the directive can be seen. For private content, use password protection rather than relying on robots.txt.

Google explains the noindex options and their limitations in its index-blocking documentation.

3. Find the sitemap WordPress already provides

Before installing another tool, check whether your WordPress site already publishes a sitemap. Google notes that content management systems such as WordPress are likely to make one available automatically. Use the sitemap your site provides if it exists and accurately lists the canonical pages you want considered for search. Google recommends absolute, fully qualified URLs and the canonical URLs you prefer for results. See Google’s sitemap overview for details.

If the existing sitemap is missing or does not meet a specific need, address that gap rather than running multiple sitemap generators that may duplicate or conflict with one another. A sitemap can be split when it exceeds Google’s documented limit of 50 MB uncompressed or 50,000 URLs; a sitemap index can point to the separate sitemap files. These limits are from Google’s current sitemap instructions.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

4. Submit the sitemap in Google Search Console

  1. Verify your site in Search Console. Add the appropriate property and complete Google’s verification process so you can manage it.
  2. Open the Sitemaps report. In Search Console, select your property and open the Sitemaps report.
  3. Submit the sitemap URL. Enter the sitemap address published by your WordPress site and submit it.
  4. Check the report. Review whether Google accessed the sitemap and whether it reports processing errors. Fix errors in the sitemap or the listed URLs, then check the report again.

Submitting a sitemap helps Google discover URLs, especially on a new site, but it is only a hint. As Google puts it, “Submitting a sitemap is merely a hint: it doesn’t guarantee that Google will download the sitemap or use it for crawling URLs on the site.”

5. Inspect important pages and request indexing when appropriate

Use URL Inspection in Search Console for a few important pages, such as your homepage, a newly published page, or a URL that has changed. It can show information about Google’s access and indexing of a URL and lets an eligible user request a recrawl. You must be an owner or full user of the Search Console property for the URL.

For many URLs, submit or update the sitemap instead of sending individual requests. Google’s recrawl instructions explain how to request indexing and what to expect.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

6. Diagnose the result and give Google time

A recrawl can take days to weeks, and requesting one does not guarantee that a page will be included in search. Google decides what to crawl and index; useful, high-quality content matters, and technical access alone is not enough.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Google cannot fetch the page: check public access, server response, DNS or firewall rules, and robots.txt; then use URL Inspection to see what Google can access.
  • Google fetches it, but it is not indexed: check for noindex, duplicate content, and canonical choices. Make sure any intended indexing directive is visible to Googlebot.
  • The sitemap is accepted, but URLs are missing: confirm it lists absolute canonical URLs that should appear in Search. Sitemap submission does not compel Google to crawl or index every listed page.

Use Search Console’s reports to monitor crawl or indexing problems and correct specific issues rather than repeatedly submitting the same page. Google’s crawling-error troubleshooting guide covers access failures.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.