Fix Google Indexing: Google Search Console Domain & Sitemap Setup Guide

When switching to a custom domain for your Tistory, Blogger, or any other blogging platform, your posts don't always appear on Google automatically. You need to explicitly tell the Googlebot: "This is my official domain, come and crawl my content!"

Many beginners encounter frustrating errors (like "Could not fetch" or "Sitemap could not be read") right after setting up a custom domain in Google Search Console.

Here is a foolproof, 4-step guide to successfully configuring your Domain Property, Sitemaps, and RSS feeds in one go.

Step 1: Create a 'Domain Property' (The Universal Container)

Instead of adding your blog as a "URL prefix" property (e.g., https://example.com), it is highly recommended to use the Domain property option.

  1. Log in to Google Search Console.

  2. Click the property dropdown menu in the top left corner and select "Add property".

  3. In the Domain box (the left option with the globe icon), type your clean root domain without https:// or www (e.g., metacog.co.kr).

  4. Follow the instructions to verify ownership via DNS record verification (simply copy the provided TXT record and paste it into your domain registrar's DNS settings).

💡 Why choose Domain Property? A single Domain Property automatically covers all protocols (http, https), subdomains (www, insight.metacog.co.kr), and paths. You can manage your entire domain ecosystem inside one clean dashboard.

Step 2: Optimize Feed & Crawling Settings (WordPress & Blogger)

Before submitting your pathways to Google, you need to ensure your blogging platform is configured to output "Full Text" feeds rather than partial snippets. This allows Googlebot to read and index your entire article context accurately.

For WordPress Users:

  1. Log in to your WordPress Dashboard and go to Settings > Reading.

  2. For each post in a feed, include: Select "Full text" (Instead of Excerpt).

  3. Set "Syndication feeds show the most recent" to 50 or higher.

  4. Click Save Changes.

For Google Blogger (Blogspot) Users:

  1. Go to your Blogger Settings > Site feed.

  2. Ensure "Allow blog feed" is set to "Full".

  3. This guarantees that your Atom/RSS feeds contain the complete HTML structure of your posts for seamless Googlebot discovery.

Step 3: Submit Sitemap & RSS via Full URL

Now, go back to Search Console to open up the crawling pathways. Navigate to the Sitemaps menu on the left sidebar.

🚨 CRITICAL: How to Avoid the "Could not fetch" Red Error If you are using a Domain Property, typing just sitemap.xml or rss into the input field will often cause Google to trigger a "Sitemap URL is incorrect" error. To fix this, you must input the absolute Full URL including https://.

Step 4: Submit Pathways for Subdomains (Blogger / Blogspot)

If you have connected a subdomain (like insight.metacog.co.kr) to Google Blogger (Blogspot) under the same domain ecosystem, you can submit its sitemap inside this exact same Domain Property.

  • The Ultimate Pro-Tip for Blogspot Subdomains: While Google has improved Blogspot's default sitemap.xml parsing, subdomains still occasionally throw indexing errors. If sitemap.xml fails, delete it and submit the Atom feed URL instead. It acts as a foolproof alternative.

  • Blogger Atom Feed Pathway (Recommended): Enter the full URL string below into the Sitemap submission box: https://insight.metacog.co.kr/atom.xml?redirect=false&start-index=1&max-results=500

Wrapping Up

Once submitted, you should see a green "Success" status next to all your paths. If it initially says "Could not fetch", don't panic—give it a few minutes, refresh the page, or re-submit using the absolute Full URL.

With these clean signposts established, Googlebot will seamlessly crawl and index your newest posts. Now that the technical heavy lifting is done, you can focus entirely on creating high-quality, valuable content!

위치: 미국 텍사스 오스틴

댓글

댓글 쓰기