Webmaster Tools Console Guide

A "webmaster tools console" is the dashboard a search engine gives site owners to see how it crawls, indexes, and ranks their pages. There are two that matter: Google Search Console and Bing Webmaster Tools. This guide explains what each console is, how to set one up, and how to fix the issues it flags, without pretending there is any magic third-party scanner in the mix.

What a webmaster tools console is (and is not)

A webmaster console is a first-party reporting tool. You prove you own a site, and in return the search engine shows you its own data about that site: how many pages it has indexed, which search queries triggered your pages, which URLs returned errors, and which sites link to you. It is not a public grader that scores any URL you type in, and there is no proprietary 404Pulse console behind this page. The consoles described here are Google's and Microsoft's, and they are free.

The phrase confuses people because the name changed. Until 20 May 2015 the Google product was called Google Webmaster Tools. Google renamed it Search Console to reflect that the audience had grown beyond "webmasters" to marketers, developers, and business owners. So when someone searches "webmaster tools console", they are almost always looking for today's Google Search Console. Our companion guide to webmasters tools covers that history and the first-week setup checklist in more detail.

Setting up the Google console

Adding a site to Google Search Console takes a few minutes. Choose a property type first: a "Domain" property covers every subdomain and protocol at once but requires a DNS verification record, while a "URL prefix" property covers one exact address and accepts several verification methods.

1. Add the property and pick a verification method: DNS TXT record, an uploaded HTML file, an HTML meta tag, or a linked Google Analytics or Tag Manager account.
2. Once verified, submit your XML sitemap in the Sitemaps tool so Google can discover your pages efficiently.
3. Wait a few days for data to populate, then start with the Pages report and the Performance report.

Each report is its own tool. For a full walk-through of the individual reports and how to act on them, see our guide to the tools inside Search Console.

Setting up the Bing console

Bing Webmaster Tools is Microsoft's equivalent, and it is worth running even if Bing sends less traffic than Google, because it also feeds results to other surfaces that use Bing's index. Setup mirrors Google's: add your site, verify by DNS record, XML file, or meta tag, and submit a sitemap. Bing offers a shortcut that imports your verified sites and sitemaps straight from Google Search Console, which saves repeating the whole process.

Bing's console publishes its own webmaster guidelines and includes a few tools Google does not, such as a keyword research view and a URL submission quota that lets you push new pages for crawling. Treat the two consoles as complementary rather than duplicate: they report on different indexes, so the same page can be indexed in one and not the other.

Reading crawl and indexing reports

Both consoles answer the same core question: can the engine find, crawl, and index your pages? In Google, the Pages report groups not-indexed URLs by reason. In Bing, the equivalent views flag crawl errors, blocked URLs, and indexed counts. The reasons overlap heavily.

• Blocked by robots.txt: a disallow rule is stopping the crawler. Remove or narrow the rule if the page should be indexed.
• Server or DNS errors: the crawler could not reach your server. Check uptime and response times.
• Not found (404): the URL is genuinely broken. Redirect it if there is a good replacement, or let it stay a clean 404 if there is not.
• Noindex: a tag or header is telling engines to skip the page. Remove it if the page should rank.

When the errors are broken links, the fix pattern is the same one covered in our guide to 404 Not Found errors: find the source of the bad link, then either fix the link or redirect the URL.

Reading query and link reports

Beyond crawl health, each console shows two things a crawler alone cannot: the queries people used to reach you, and the sites linking to you. Google's Performance report and Bing's search performance view both list impressions, clicks, and average position by query. The move is the same in both: find queries where you rank on the edge of page one, then improve the matching page to climb.

Both consoles also report inbound links. Google's Links report and Bing's backlinks view give a sample of who points at you and with what anchor text. They are samples, not complete audits, so pair them with a dedicated checker as covered in our guide to checking incoming links.

Common console problems and how to fix them

A handful of issues account for most of the alarm in a webmaster console. Here is how to clear the frequent ones:

• Sudden drop in indexed pages: check for an accidental site-wide noindex or a broken robots.txt deployed with a recent release.
• "Discovered, currently not indexed" growing: often a crawl-budget or quality signal on large sites. Strengthen internal linking and prune thin pages.
• Manual action or security notice: read the exact reason, fix it, then use the console's "Request review" button. Never ignore these.
• Mobile usability or experience warnings: fix the shared template, then use "Validate fix" so the engine rechecks the whole group.

Keeping two consoles in a single routine

Running Google and Bing consoles does not mean doubling your workload. Because they report on different indexes but flag the same categories of problem, you can review them in one sitting. A practical monthly routine looks like this:

• Indexing first: in each console, confirm your key pages are indexed and scan the not-indexed reasons for anything new since last month.
• Errors next: clear any fresh crawl errors, especially 404s and server errors introduced by a recent release.
• Performance last: note queries where you rank just off page one in either engine, since a fix on one page often helps in both.

Because Bing can import your verified properties and sitemaps from Google, keeping the two in sync costs only a few minutes. Treat the second console as a free second opinion on the same site, not as a separate project.

Where the console fits in a wider toolkit

The two consoles are the foundation, but they do not do everything. They will not estimate a competitor's traffic, run a full technical crawl of thousands of URLs at once, or research keywords at scale. For those jobs you add a crawler and a research tool. Our overview of search engine optimisation tools shows which free options fill each gap around the consoles.

Frequently asked questions

Is "webmaster tools console" the same as Google Search Console?

Yes, in almost every case. Google's product was called Google Webmaster Tools until it was renamed Search Console on 20 May 2015. When people search for a webmaster tools console today, they are usually looking for Google Search Console.

Do I need both Google and Bing consoles?

You do not strictly need both, but running both is free and worthwhile. They report on different indexes, so a page can be indexed in one and missing from the other, and each console explains problems the other cannot see.

Is a webmaster console free?

Yes. Both Google Search Console and Bing Webmaster Tools are completely free. You only need an account with the provider and the ability to verify that you own the site.

How do I verify ownership of my site?

Both consoles accept several methods: adding a DNS TXT record, uploading an HTML verification file, adding an HTML meta tag, or linking an existing analytics or tag manager account. Pick whichever you can edit most easily.

Can a webmaster console show a competitor's data?

No. A webmaster console only shows data for sites you have verified ownership of. To research a competitor you need a third-party estimation tool, which models the data rather than reading it from the real console.