Search Console and Bing guide

Add your GoodSender blog to Google Search Console and Bing Webmaster Tools

Prove you own the blog, hand each search engine its sitemap, and watch your posts get indexed. Your blog already publishes everything the engines need; the only choice is how you verify, and that depends on where the blog lives.

Updated October 20, 2026

What your blog already publishes

Every GoodSender blog serves these files at its own address, kept current on every publish. There is nothing to generate, upload or resubmit. Replace blog.example.com with the address your readers use: your custom domain, or your GoodSender address (yourname.gsnd.io).

Address	What it is
`https://blog.example.com/sitemap.xml`	Your sitemap: every published post with its last-modified date, plus the pages that list them (the archive, and the home page on themes with a separate landing page). This is the URL you submit to both consoles.
`https://blog.example.com/robots.txt`	Allows every crawler and names the sitemap, so engines that read robots.txt find it even before you submit.
`https://blog.example.com/rss.xml`	The RSS feed of your posts, for readers and feed-based discovery.
`https://blog.example.com/llms.txt`	A plain-text index for AI answer engines, following the llms.txt convention.

Each page also carries a canonical URL, a title, a description from your summary, and Open Graph and Twitter cards with your cover image. If you use both a custom domain and a GoodSender address, each address serves its own sitemap; verify and submit the one you link to.

Google Search Console

Open search.google.com/search-console with the Google account that should own the data, and pick the property type that matches where the blog lives.

Step 1: Choose and verify a property

Standalone blog on its own domain

Example: myblog.com, connected as your custom domain.

Add a Domain property for myblog.com. It covers http and https, with and without www, and every subdomain, so you set it up once.
Verify with the DNS TXT record Google shows: add it at the DNS provider where you already added GoodSender's records for this domain, then press Verify. DNS changes can take minutes to a few hours to be seen; the record stays, so verification does not lapse.

Blog on a subdomain of a site you already verified

Example: blog.example.com, where example.com is already in Search Console.

If example.com is a Domain property, there is nothing to verify: it already includes the blog. Go straight to the sitemap step and submit the blog's sitemap URL there. The blog's pages show up in the same reports, and you can filter them by URL.
If the main site is a URL-prefix property such as https://www.example.com/, it does not cover the subdomain. Either upgrade to a Domain property for example.com (DNS TXT, as above), or add a URL-prefix property for https://blog.example.com/ and verify it with the Google Analytics or Tag Manager method below. Prefer a separate URL-prefix property for the blog if you want its reports on their own.

Blog on your GoodSender address

Example: yourname.gsnd.io. You cannot add DNS records, upload files or place meta tags there, which rules out the DNS, HTML file and HTML tag methods. Two methods remain, and both work because GoodSender places your tag in the page head.

First connect Google Analytics (or Tag Manager) in Configuration and confirm the tag fires on the live blog. Verification checks the live page, so the blog must be live and the tag present.
Add a URL-prefix property for https://yourname.gsnd.io/, with the exact scheme and a trailing slash.
Under Other verification methods, choose Google Analytics if you pasted a G- id (you need the Edit role on that property), or Google Tag Manager if you pasted a GTM- container (you need Publish permission on it). Press Verify.

Keep the tag in place afterwards: Search Console re-checks ownership periodically and un-verifies a property whose method disappears.

Step 2: Submit the sitemap

In the property, open Indexing → Sitemaps.
Under Add a new sitemap, enter the sitemap address. In a URL-prefix property the prefix is filled in, so type sitemap.xml; in a Domain property enter the full URL, https://blog.example.com/sitemap.xml.
Press Submit. The status reads “Success” once Google has fetched it, usually within a day, and shows how many URLs it discovered.

Step 3 (optional): Ask for your first pages

Paste the blog's home page and your first few posts into the URL inspection bar at the top and press Request indexing for each. Google crawls a new site in its own time; this nudges the first pages forward. You do not need to repeat it for later posts: the sitemap announces them.

Bing Webmaster Tools

Bing's index also powers DuckDuckGo, Yahoo and Ecosia, so one submission covers them all. Sign in at bing.com/webmasters with a Microsoft, Google or Facebook account.

Option A: Import from Google Search Console (every hosting shape)

On the My Sites page choose Import, sign in with the Google account that holds your Search Console property and allow Bing to read your list of verified sites and sitemaps.
Tick the blog's property and press Import. It arrives verified, with its sitemaps, and no second verification is needed. This is the only route for a blog on a GoodSender address, and the quickest for every other one.

Option B: Add the site yourself (custom domain)

Choose Add a site manually and enter https://blog.example.com/.
Pick the CNAME record method and add the record Bing shows at your DNS provider. The XML file and meta tag methods are not available on a GoodSender blog, because you cannot place files or tags on it.
Press Verify once the record is live.

Then: Submit the sitemap

Open Sitemaps in the left menu, press Submit sitemap, enter the full URL https://blog.example.com/sitemap.xml and submit. An imported site may already list it; if so, you are done.

After you submit

Indexing takes days to weeks for a new site. “Discovered – currently not indexed” in Google's Pages report is normal early on; it clears as the engine learns the site.
Nothing to resubmit. Each publish updates the sitemap and its last-modified dates; both engines re-read it on their own schedule.
Performance in Search Console and Search Performance in Bing show the queries that bring readers to each post once there is traffic to show.
What the engines display comes from your posts: the title, the summary you write in the composer, and the cover image. Good summaries are the lever you control.

Troubleshooting

Sitemap: “Couldn't fetch”: Open the sitemap URL in your browser. If it does not load, the blog is not live yet: on a custom domain, the Domain page must show HTTPS connected. Check the host too: a sitemap submitted under www. or under the GoodSender address when readers use the custom domain points at a different site.
Google Analytics verification fails: The tag must be live on the page when you press Verify: save the id in Configuration, wait a minute, and confirm it in Realtime first. You need the Edit role on the Analytics property, and a GTM- container needs the Tag Manager method, not the Analytics one.
The blog does not appear in my Domain property: Submit the blog's sitemap in that property and give it a few days; then filter the Pages report by the blog's URL prefix. A Domain property only includes the subdomain if the blog really runs under that domain.
A post is missing from the sitemap: Only published posts are listed. Drafts and scheduled posts join the sitemap when they go live.

Menu names above are Google's and Microsoft's as of October 20, 2026; both consoles rename things from time to time, but the methods stay the same.