How to Set Up Google Search Console and Submit Your WordPress Sitemap Correctly

Learn how to verify your WordPress site in Google Search Console, submit XML sitemaps, check indexing status, and fix common crawl errors the right way.

Why Google Search Console Matters for Your WordPress Site

Google Search Console (GSC) is a free tool from Google that shows how your site appears in search, which pages are indexed, and what technical issues may be blocking visibility. It also lets you submit sitemaps so Google can discover your content more efficiently.Source

Step 1: Create or Access Your Google Search Console Account

Before you can verify your WordPress site, you need access to GSC.

1. Sign in to your Google account (preferably a business or shared account for your organization).
2. Go to the Google Search Console home screen.
3. Click Start now and you’ll land on the property setup screen.

Step 2: Choose the Right Property Type

Google offers two main property types:Source

• Domain – Covers all protocols and subdomains (http, https, www, non-www, subdomains).
• URL prefix – Covers only one exact URL pattern (for example, https://www.example.com/).

Recommended: Use a Domain property if you can update DNS records. This gives the most complete data.

How to Add a Domain Property

1. In GSC, under “Select property type”, choose Domain.
2. Enter your domain without protocol (e.g., example.com).
3. Click Continue. Google will show a DNS TXT record.

How to Add a URL Prefix Property

1. Choose URL prefix.
2. Enter your full site URL exactly as it loads in the browser (including https:// and www if used).
3. Click Continue to see verification options.

Step 3: Verify Site Ownership

You must prove you control the site before Google will show full data. Common verification methods include DNS, HTML file upload, and meta tag.

Method 1: DNS TXT Record (Best for Domain Properties)

1. Copy the TXT record provided by GSC.
2. Log in to your domain registrar (e.g., where you bought your domain).
3. Find the DNS management area and add a new TXT record for your root domain.
4. Paste the value from Google and save.
5. Return to GSC and click Verify. DNS changes can take several minutes to propagate.

Method 2: HTML File Upload (Common for URL Prefix)

1. In GSC, choose the HTML file verification method.
2. Download the file Google provides.
3. Upload it to your WordPress site’s root directory via your hosting file manager or SFTP.
4. Confirm the file is accessible in a browser.
5. Click Verify in GSC.

Method 3: HTML Tag via a Plugin

If you prefer not to touch DNS or server files, you can use a plugin to add the verification meta tag.

1. In GSC, choose the HTML tag method and copy the meta tag.
2. In WordPress, install a trusted SEO or header management plugin that supports Search Console verification.
3. Paste the meta tag into the plugin’s verification field and save.
4. Return to GSC and click Verify.

Step 4: Generate and Confirm Your WordPress XML Sitemap

WordPress can generate sitemaps natively, and many SEO plugins (like Yoast SEO) provide enhanced sitemaps.

Using Native WordPress Sitemaps

Recent versions of WordPress automatically generate a basic XML sitemap at /wp-sitemap.xml.Source

• Visit https://yourdomain.com/wp-sitemap.xml in your browser.
• If you see a list of sitemap index files, your native sitemap is active.

Using Yoast SEO Sitemaps

1. In WordPress, go to Dashboard ? Plugins ? Add New and install Yoast SEO if it’s not already active.
2. Go to SEO ? General ? Features.
3. Ensure XML sitemaps is set to On and save changes.
4. Click the question mark icon next to XML sitemaps and open the sitemap link, typically /sitemap_index.xml.Source

Important: Avoid serving multiple conflicting sitemaps. If you use Yoast, it’s fine that the native sitemap exists, but you should submit only one primary sitemap in GSC (usually the Yoast index).

Step 5: Submit Your Sitemap in Google Search Console

1. In GSC, select your verified property.
2. From the left menu, click Sitemaps.
3. Under “Add a new sitemap”, enter the sitemap path only (for example, sitemap_index.xml or wp-sitemap.xml).
4. Click Submit.

GSC will show the status of your sitemap (Success, Has issues, or Couldn’t fetch). You can click into the sitemap to see discovered URLs and any reported problems.Source

Step 6: Check Indexing Status

Once your sitemap is submitted, you can monitor which pages are indexed.

1. In GSC, go to Indexing ? Pages (or a similarly named report).
2. Review the Indexed vs Not indexed counts.
3. Click into Not indexed to see reasons (e.g., Excluded by ‘noindex’, Duplicate, Crawled – currently not indexed).
4. Use the URL inspection tool to check individual URLs and request indexing when appropriate.

What You Should See

• Your sitemap listed under Sitemaps with a status of Success.
• Gradual growth in the number of Indexed pages over time.
• Reasonable explanations for any Not indexed URLs (for example, intentionally noindexed pages like thank-you screens).

Common Crawl and Indexing Errors (and How to Fix Them)

1. Server Errors (5xx)

What it means: Googlebot tried to access a page but your server returned a 5xx error (e.g., 500, 503).Source

How to fix:

• Check hosting resource limits and uptime.
• Review error logs for PHP or plugin conflicts.
• Temporarily disable heavy plugins or caching rules causing timeouts.

2. Not Found (404)

What it means: Google is trying to crawl URLs that no longer exist.

How to fix:

• If the page moved, set a 301 redirect to the new URL.
• If the page is intentionally removed and has no replacement, leaving a 404 is acceptable.
• Update internal links and menus to avoid linking to missing pages.

3. Soft 404

What it means: The page returns a 200 (OK) status but appears empty or like an error page to Google.

How to fix:

• Ensure real error pages return a proper 404 status.
• Add meaningful content to thin pages that should be indexed.
• Redirect low-value or duplicate pages to more relevant content.

4. Blocked by robots.txt

What it means: Your robots.txt file is preventing Google from crawling certain URLs.

How to fix:

• Check https://yourdomain.com/robots.txt.
• Remove overly broad Disallow rules that block important content.
• Ensure your sitemap URL is not disallowed.

5. Excluded by ‘noindex’

What it means: A noindex directive in meta tags or HTTP headers tells Google not to index the page.

How to fix:

• In WordPress, edit the page or post and check your SEO plugin’s settings.
• Remove noindex from pages that should appear in search.
• Keep noindex on low-value or private pages (e.g., internal search results, login pages).

Ongoing Monitoring: What to Check in Search Console

To keep your WordPress site healthy in search, review these areas regularly:

• Indexing ? Pages: Watch for sudden drops in indexed pages.
• Sitemaps: Ensure your sitemap continues to show Success and a growing URL count as you publish.
• Experience / Page Experience: Monitor Core Web Vitals and mobile usability.
• Security & Manual Actions: Confirm there are no manual penalties or security issues.

AI Prompt: Generate a Custom Search Console Monitoring Checklist

You can use this prompt with an AI assistant to generate a monitoring checklist tailored to your site:

Act as an SEO analyst. Create a Google Search Console monitoring checklist for a WordPress site with [NUMBER OF PUBLISHED PAGES] pages, focused on [PRIMARY GOALS, e.g., lead generation, ecommerce sales, local visibility].

Include:
- Weekly checks (indexing, coverage, key queries, and pages)
- Monthly checks (Core Web Vitals, mobile usability, structured data)
- Quarterly checks (content pruning, sitemap review, internal linking issues)
- Specific alerts or thresholds that should trigger deeper investigation

Format the output as a table with columns: Frequency, Task, Report/Tool in GSC, What to Look For, Action if Problem Found.

Replace the bracketed sections with your site’s actual page count and goals before using the prompt.