Google Search Console for retail websites

Set up Google Search Console for your retail site. Verify access, inspect product URLs and use query reports to find gaps in your published answers.

Google Search Console shows how your retail website appears in Google Search and helps you investigate pages Google cannot index. Verify the store property, inspect a product URL and use query reports to find questions your published pages leave unanswered.

What Search Console shows and what it does not

Google Search Console is a free service for monitoring your site’s search presence. Google previously called it Webmaster Tools. Registering is optional for appearing in search results.

For a retail website, its reports show search queries, clicks and indexing information. They can reveal that a product page appears for a question about its dimensions. They do not tell you whether that visitor later opens a size chart or completes checkout. Use on-site analytics for those actions.

Search exposure also differs from Instagram account insights. Google now documents separate platform properties for supported social accounts, with availability rolling out gradually. Those measure discovery through Google. An Instagram profile is not a verified property for your retail website, and its Google exposure is separate from activity inside Instagram. Google’s property guide explains the distinction.

Sign in and verify the right property

Sign in with your own Google account, then select or add the property that covers your store’s public URLs. Signing in identifies you. Property access gives that account permission to see a particular site. Verification proves ownership through control of the site or its domain.

Choose a Domain property when you control domain records and need coverage across subdomains and protocols. Enter the domain without a protocol or path. A URL-prefix property covers the exact protocol, hostname and optional path you enter. For example, https://www.example.com/ excludes the non-www hostname and HTTP version.

Add and verify the website

  1. Open Search Console and choose Start now. Use the property selector to choose Add property.
  2. Choose the website property type and enter the domain or full URL prefix.
  3. For a Domain property, publish the DNS verification record Google supplies through your domain provider. Keep existing records intact.
  4. For a URL-prefix property, choose a supported method you control. Options include an HTML verification tag or file, DNS and eligible Google Analytics or Tag Manager access.
  5. Select Verify. Confirm success and open the property. Keep the verification record or tag in place because Google checks ownership again.

An HTML tag belongs in the public homepage’s head. A verification file must be available at the exact location Google specifies. A password-protected homepage can prevent tag verification. Google’s verification instructions give requirements for each method.

Use your store platform’s supported method

  • On Shopify, use its verification and sitemap procedure. For HTML-tag verification, add Google’s tag to the published theme’s theme.liquid, below the opening head tag, then save and verify. Remove storefront password protection before Google checks it. Shopify generates /sitemap.xml for the store.
  • For BigCommerce, the Domain-property method works through your domain’s DNS provider, independently of storefront theme settings. Once verified, submit the store’s actual public sitemap URL through Google’s Sitemaps report. If a developer manages the storefront, obtain the sitemap address from them instead of guessing an admin field or file location.
  • On Wix, an owner or admin collaborator can use the SEO Setup Checklist. Complete its first step and choose Connect to Google. This requires a Premium site with a connected domain. Wix submits the sitemap automatically through this connection.
  • In Webflow, copy the verification ID from Google’s HTML tag. Paste the ID in Site settings, under SEO and Google site verification, then save and publish. Return to Google and verify. Webflow’s verification instructions distinguish the ID from the complete tag. Enable Auto-generate sitemap in the SEO settings, save and publish to create /sitemap.xml.
  • On WordPress with Yoast SEO, choose HTML tag in Search Console. In Yoast SEO, open Settings, then Site connections, paste the tag under Google and save. Return to Google and verify using Yoast’s instructions for this verification step. Its sitemap index is normally /sitemap_index.xml. Google’s Site Kit plugin separately connects Search Console reporting to the WordPress dashboard.

For Webflow, the sitemap setup guide covers publishing. For Yoast, its sitemap submission guide covers the index URL. Check that the chosen sitemap loads publicly before submitting it.

Grant access without sharing credentials

A property owner can give colleagues access through Settings, then Users and permissions. Give each person access through their own Google account.

Owners control settings and user access. A verified owner proves control with a verification token. A delegated owner receives ownership from another owner.

Full users can view data and take some actions. Restricted users have limited viewing rights. Google’s permissions guide lists the differences.

To add a user, open Users and permissions, select Add user and enter their Google account address. Choose the required role and select Add. To remove a user, use the menu beside their entry and select Remove access. Removing a verified owner also requires removing their ownership tokens, or they can verify again.

If a property is missing, check the signed-in account and property selector first. Ask an existing owner to confirm your account has access. If the only verified owner has left, an authorised operator must verify ownership again. Access to the store administration alone does not automatically grant Search Console access.

The published google-site-verification tag proves control through its location. It is different from a private password or authentication code. Keep login credentials private. For account sign-in problems, use Google’s account recovery guidance. For verification errors, use the Search Central Help Community with the error and affected public URL, excluding private account details.

Inspect and request indexing for a URL

URL Inspection distinguishes Google’s stored information about a URL from a test of the page available now. The initial result is not a fresh crawl of your latest edit.

  1. Select the store property and paste a complete product URL into the inspection bar.
  2. Read the indexing result. Expand the indexing details to check the last crawl and Google-selected canonical URL.
  3. After a correction, choose Test live URL. Check whether Google can fetch the current page and whether indexing is allowed.
  4. When the intended page is indexable, choose Request indexing on its inspection result. Google runs a check before adding an eligible URL to the queue.
  5. Return later to compare the recorded crawl and indexed information with the changed page.

A successful live fetch confirms access during that test. It does not establish that Google has indexed the page. A request has limits and cannot guarantee inclusion or a completion time. Google’s URL Inspection guide explains the results and request procedure.

For a collection of URLs, submit a sitemap instead of repeatedly requesting each page. Open Sitemaps in the verified property, enter the public sitemap address and select Submit. For a Domain property, include the full sitemap URL. Check for Success or open the submission’s error details. Google’s Sitemaps report instructions specify owner access for submission through that report.

Interpret indexing outcomes

OutcomeCheckNext action
Page with redirectFollow the redirect and inspect the destinationKeep an intended redirect. Submit and internally link the final product URL
Soft 404Open the page and inspect its content and responseRestore useful product content, or return a genuine 404 or 410 for a removed page
Crawled, currently not indexedRead the crawl details and inspect the page’s usefulness and duplicationCorrect the identified issue. Repeated submissions alone do not resolve it
Fetch blockedCheck login requirements, server errors and crawl controlsRestore intended public access before testing again

Google’s Page indexing report explains these statuses. A discontinued product that redirects to an unrelated category needs review even when the redirect itself works.

Read the performance report by query and page

The Performance report measures search-result exposure and clicks within its selected period, search type and filters. Start by setting those controls before comparing numbers.

A click records a click from Google Search to your site. An impression records an appearance under Google’s counting rules. Click-through rate (CTR) is clicks divided by impressions. Average position describes the topmost result for the relevant property or grouping, averaged across its impressions.

A position of eight is an average across searches, not a promise that every customer sees your page eighth. Search layouts and the selected grouping affect interpretation. Google’s report guide defines the metrics and controls.

  1. Choose Search results and a period long enough for the question you are investigating.
  2. Select the search type, such as Web or Image. Keep that choice consistent across comparisons.
  3. Use Queries to find a product question, then select it to filter the report.
  4. Switch to Pages to see which URLs receive exposure for that query. Use country and device filters when those distinctions affect the answer.
  5. Compare equivalent periods with the same filters. Keep the selected settings with any exported report.

Recent figures can be preliminary and change as Google finishes processing them. Use the report’s latest available data indicator before treating a partial period as a decline. Report totals also depend on aggregation. Query rows omit anonymised searches, and page data commonly belongs to Google’s selected canonical URL. Google explains these data differences.

Google includes AI Overviews and AI Mode in overall Web search performance. A rise in impressions alone cannot prove that a page appeared in an AI Overview. For a sudden drop, compare query groups and affected pages, then inspect indexing and site changes before assigning a cause.

Turn product questions into better published answers

Use the query and page together to find the public answer a customer needs. Search Console gives evidence of exposure for your site, not the total market’s search volume.

Consider a fictional report for a lighting store. Over four complete weeks, the query “can the cedar wall light go outside” has 240 impressions and six clicks. Its CTR is 2.5%. The Pages tab attributes this query to /products/cedar-wall-light/.

The product page says “suitable for outdoor spaces”, but omits the manufacturer’s covered-location restriction. The retailer checks the supplied installation instructions and confirms the fitting is for sheltered outdoor locations only. That missing condition changes the purchase decision.

  1. Correct the product page to state the sheltered-location requirement beside the suitability information. Include the manufacturer’s supported rating and installation restrictions where supplied.
  2. Check the relevant advice page and product specification table for the same wording. Correct any conflicting claim using the same source.
  3. Open the public product URL after publishing. Confirm the answer appears without signing in and that its links reach the intended instructions.
  4. Use Test live URL to check Google can retrieve the corrected page. Request indexing if appropriate, then revisit the stored crawl information later.

Keep the original report and compare a later equivalent period using the same filters. The immediate result is a supported answer at the correct URL. Any later traffic change needs separate analysis. These fictional numbers demonstrate the workflow and establish no ranking improvement.

Use removals and specialist tools carefully

Temporary removal hides a result in Google Search. It does not delete the source page or restrict who can visit it.

For an urgent search-result removal on your own property, open Removals and create a temporary removal request for the correct URL or prefix. Review its scope before submitting. Google’s Removals instructions explain its approximately six-month duration and the additional work required for permanent removal.

For permanent removal, delete the source with an appropriate missing-page response, require authentication or apply noindex while allowing Google to crawl it. Choose the control that matches whether people must still access the content. A robots.txt block alone is insufficient to remove an indexed URL. Removing a URL from a sitemap also leaves the page itself available.

The separate disavow tool concerns incoming links. Google says most sites do not need it. Its disavow guidance requires both substantial problematic backlinks and a manual action, or a likely manual action, before considering it. Incorrect use can harm search performance.

If your store has a link-related manual action, obtain specialist review of the links and removal options before uploading a file. For an ordinary product-page correction, publish the supported answer and verify the URL instead.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup