Guide

    See What Your Magento Store Ranks For, in Plain English

    Free checks for rankings, technical faults and whether AI assistants name you

    By Simon Bumford, Founder of EveryHost11 min read

    TL;DR

    Disclosure first: EveryHost built Sondavo, so this is our own product, not a neutral review. We built it because hosting customers kept asking what their store ranked for and we could not give a straight answer. Sondavo runs a free check on any site with no sign-up, and publishes eight free tools that map almost one to one onto the places Magento stores go wrong: canonical tags on layered navigation URLs, robots.txt rules, sitemaps, redirect chains left by a migration, and the x-robots-tag header that hides a page from Google invisibly. It also asks ChatGPT, Claude, Gemini and Perplexity your market's real questions and records who gets named. It is not Magento-specific and it does not replace a developer, but it tells you what is wrong in language you can hand to one.

    The question we could not answer

    Start with the disclosure, because it changes how you should read everything below. EveryHost built Sondavo. It is our product, we make money from it, and this article exists partly to tell Magento merchants it is there. We are not reviewing it from the outside and we are not pretending to be neutral about it.

    Here is why it exists. Several times a month a hosting customer would arrive with a version of the same question: traffic is down, or a rival is above us, or the store feels invisible, so is it the server? Sometimes it genuinely was, and we could prove that in minutes. Far more often it was not, and the honest answer was that we had no idea, because we could see response times and error rates and nothing at all about search. So we built the thing we kept wishing we could hand people: tell a site owner where they stand, what is moving and what is broken, using their own data wherever possible, in words a shop owner can read without a glossary. Judge what follows on whether the checks are useful to you, not on our enthusiasm for our own work.

    Depth, not rank: what one free check shows

    The name is nautical. A sounding measures how deep the water is under a vessel, and Sondavo asks the equivalent question of a website: how deep does this site sit in search? Position one is the surface, everything below it is depth, and the further down a page sits the less light reaches it. Position eleven is not one worse than position ten, it is a different world, because it is page two.

    The free check at sondavo.com needs no sign-up and returns three things. Where you stand: the searches your site already appears for, plotted at their true depth rather than flattened into an average. What is rising, which the product calls shoaling, borrowing the word for a seabed coming up toward the surface. Those are the keywords sitting just under page one, ranked by a deterministic engine so every score traces back to the rule that produced it. And what is holding you back: a polite crawler surveys the site the way search engines read it, and reports what it finds in plain English.

    For a Magento merchant the middle one is usually what to act on this month. A keyword at position thirteen is one decent internal link, one honest category description and one fixed canonical tag away from page one. A keyword at position ninety is a project. Knowing which terms are shoaling turns a vague ambition to do some SEO into a short list of specific pages.

    Position 1the surfacePosition 10page one endsPosition 30Position 90brand nameproduct SKUcategory termhead termbuying guideshoalingposition 13, risingDeeper means less light:position 11 is not one worse than 10, it is page two.
    Rankings plotted as depth. The terms sitting just under the page one line are the ones worth a week of work.

    Eight free checks, and the Magento faults they catch

    The eight tools at sondavo.com/tools need no account and no card. None was built for Magento, and that is the point: they look at a site the way a crawler does, from outside, which is exactly the vantage point from which Magento's characteristic problems become obvious. Magento generates URLs at a scale no other common platform matches, and every generated URL is a chance for a canonical tag, a robots rule and a sitemap entry to disagree with each other.

    Website keyword checker

    Answers the question merchants ask first: what keywords does my website rank for? Enter a domain, get the searches it appears for with positions and monthly volumes.

    On a Magento store: Run it on your store, then on the two rivals you lose deals to. The searches they appear for and you do not are a shopping list of missing categories and thin product copy.

    robots.txt checker

    Reads your robots.txt and tells you plainly who is shut out: Google, Bing, or the AI assistants.

    On a Magento store: Magento stores accumulate robots rules over years of filter-URL firefighting, and a rule written to block one parameter pattern very often blocks more than intended.

    Canonical tag checker

    Shows whether a page points its canonical tag at itself or hands its standing to another URL.

    On a Magento store: The single most valuable check on a Magento category page. Layered navigation multiplies URLs, and the canonical tag is what stops those variants competing with the clean one.

    Redirect checker

    Follows every hop in a redirect and shows the status code at each step, so a chain or a loop becomes visible rather than invisible.

    On a Magento store: Redirect chains are a classic migration artefact: old category URLs remapped during a replatform, then again in a URL-key tidy-up, with nobody noticing the two hops stacked up.

    HTTP header checker

    Lists the response headers a URL returns, including x-robots-tag, the header that can hide a page from search invisibly.

    On a Magento store: Staging noindex headers left on in production is a real and recurring Magento accident, and nothing in the page source gives it away.

    Sitemap checker

    Counts the addresses listed in your sitemap and shows a sample of them.

    On a Magento store: Magento generates its sitemap on a schedule. A count far larger than your product and category totals means filtered URLs have leaked in; far smaller means generation is failing quietly.

    SERP snippet preview

    Renders how a title and description will actually appear in results, measured in pixels rather than characters, for desktop and phone separately.

    On a Magento store: Magento titles built from attribute templates run long fast. Brand, model, size, colour and pack quantity in one string gets cut off mid-word on a phone.

    hreflang checker

    Lists every hreflang tag on a page and tells you whether x-default is present.

    On a Magento store: Multi-store-view Magento setups serving en-GB, en-IE and de-DE are exactly the case hreflang exists for, and where a missing x-default sends the wrong storefront to the wrong shopper.

    If you do one thing from this article, run four of those on a single category URL in this order: robots.txt, canonical, sitemap, HTTP headers. Is the page allowed to be crawled at all. Does it claim itself as canonical, or hand its standing to a filtered variant. Is it actually in the sitemap you submitted. Do the response headers quietly countermand all three. Four checks, four minutes, no account. If they all come back clean, the problem is content or links rather than plumbing, which is worth knowing before you spend money on either.

    Upgrades and migrations: get the baseline first

    The most expensive SEO mistake in Magento is not a bad decision, it is an absent record. A store moves to a new server, or upgrades from 2.4.6 to a current release, and four weeks later somebody says traffic is down. Down from what? Nobody wrote it down, so the conversation that follows is guesswork, and fixes that come out of guesswork are expensive.

    Both events can genuinely move rankings, for mechanical reasons. An upgrade can change URL keys, regenerate the sitemap, alter how canonical tags are emitted on filtered pages, and shift the theme's markup enough that Google recrawls the lot. Our guide to the Magento 2.4.9 hosting requirements covers the stack side of that work. A migration adds its own hazards: old category addresses remapped once, then remapped again during a tidy-up, leaving two-hop and three-hop chains that dilute the signal at every step. Our Magento migration service handles the redirect map as part of the move for that reason, and the redirect checker is how you verify afterwards that the map does what the plan said.

    So take the baseline before the work starts. Record the searches you appear for and at what depth, save what your top twenty pages earn in clicks, and run the canonical, robots, sitemap and header checks on one product page, one category page and the homepage. It costs an hour. Afterwards, when somebody says traffic is down, you are comparing against evidence instead of memory.

    Does ChatGPT mention your website?

    A growing share of the questions that used to start on Google now start in an assistant, and plenty of them are shopping questions: best waterproof work boots for cold storage, who supplies replacement seals for this pump, which UK retailer stocks this brand in a size fourteen. The assistant answers with a shortlist of names. You are on it or you are not, and unlike a search result there is no page two to be on.

    Checking this properly is harder than it sounds, because asking once proves nothing: assistants vary their answers between runs, and location changes them too. Sondavo's AI visibility feature puts your market's real questions to four engines, ChatGPT, Claude, Gemini and Perplexity, plus Google AI Overviews, on a schedule. It stores the answers verbatim so you read the actual words rather than a score, shows who was named, and lists the pages that were cited. It runs UK-located where the engines support that, which matters for a British retailer whose rivals in a US-located answer are firms that do not ship here.

    The second half is more of a build and hosting question. Sondavo also scans whether AI agents can use your site at all: whether the menus can be opened, whether the links can be read, whether there is an llms.txt summary, and whether robots.txt takes a deliberate position toward AI crawlers rather than an accidental one. A heavily JavaScript-driven Magento storefront can be perfectly usable by a human and close to opaque to an agent, and a robots.txt written in 2019 may be blocking assistants you would like to be cited by. For the traffic side there is a related feature that reads your own server log and separates the AI agents that can cite you from the ones only collecting training data.

    A shopper asks"best UK supplier forcold-store work boots?"ChatGPTClaudeGeminiPerplexityWho gets namedA competitorYour storeAnswer stored verbatimCited pages listedUK-located where supportedThere is no page two in an AI answer: you are on the shortlist or you are not.
    The same question, asked of four engines on a schedule, with every answer kept so you can read who was named and which pages were cited.

    No invented numbers

    This is the part we are most willing to be judged on, because it is where the category most often disappoints people. The rule is stated plainly: no invented numbers, ever. Every figure comes from one of three places. Your own Google data, read through Google's official read-only Search Console API, so clicks and impressions are exact rather than modelled. Your own site, crawled by Sondavo's own crawler. Or a licensed third-party index, kept separate from your own data and always labelled as an estimate.

    Two consequences follow. When a data source is not connected the interface says so, rather than filling the gap with a plausible chart. And there are no simulated previews or sample data dressed up as your results, a discipline that costs some polish on day one and is why the numbers mean anything on day thirty. Anything you check stays private by default.

    The opportunities list works the same way. Fixed rules, not a language model, so the same data in produces the same list out, and every item carries its evidence and the rule it fired on. If it says a page has a canonical problem, it shows you the tag. That matters when you hand work to a developer or an agency, because a finding you can point at is one somebody can act on without a debate about where it came from.

    What is free, and what is not

    The eight tools above are free and unconditional: no sign-up, no card, no email. Beyond them a free plan at zero pounds covers one site and, in the product's own words, is not a trial: it works forever. That is a weekly site survey, three months of history and three AI answers a day, still with no card.

    The paid plans buy frequency, depth and breadth rather than access to hidden results. Starter at nineteen pounds a month surveys every three days, holds six months of history, allows ten AI answers a day, and adds CSV export and email alerts. Professional at forty-nine pounds a month is where most single-store merchants land: ten sites, a daily survey, thirteen months of history, competitor tracking, AI visibility, twenty-five AI answers a day, three teammates and API access. Agency at one hundred and forty-nine pounds covers fifty sites, twenty-four months of history, fifteen teammates and white-label client reports.

    The wider product adds up to sixteen months of your own Search Console history, a site survey reporting eighteen kinds of technical fault in plain English, a page-by-page ledger putting each finding next to the clicks that page earns, competitor standings, verified backlinks and long tail clustering. Site fixes are separate, quoted first, with no fee if a fix does not pass a re-check.

    What it is not

    Sondavo is not a Magento product. It works on any website and knows nothing about Magento's internals. It will tell you a category page carries a canonical tag pointing somewhere unexpected. It will not tell you which admin setting, extension or theme override produced that tag, because it never sees inside your store. Everything it reports comes from outside, the way a search engine sees you.

    It also does not replace a developer. Magento's SEO surface, URL rewrites, layered navigation config, sitemap generation and store-view scoping, is genuinely intricate. What a good diagnosis does is let you brief a developer precisely instead of paying them two days to find out what is wrong. It turns a vague worry into a specific ticket.

    And it will not fix a slow store. No amount of canonical tidying compensates for a category page that takes four seconds to respond. If the checks come back clean and the store still feels invisible, look at speed next.

    Where hosting actually comes into it

    Some of what search engines and AI agents judge you on is squarely a hosting matter. Response time under crawl load is one: a store that answers quickly for a human browsing three pages can crawl badly when Googlebot requests two hundred URLs a minute, and a crawler that times out indexes less of your catalogue. Correct status codes are another, and so is serving a redirect map cleanly rather than through rewrites bolted on over the years.

    On EveryHost plans the stack is built to your store's required versions rather than one fixed recipe, and sized against your real catalogue and traffic. If you are moving a store, our managed migration includes the redirect map and the post-move verification, the single most common place rankings get lost. More broadly, our Magento 2 hosting UK plans cover the server, the stack and the go-live, and an engineer will talk the plan through before you commit to anything.

    Either way, run the free checks first. They cost nothing, they take minutes, and they will tell you whether the problem you are about to spend money on is the one you actually have.

    Frequently Asked Questions

    Frequently Asked Questions

    You have two honest routes. Google Search Console is free, belongs to you, and reports the exact queries that brought clicks and impressions to your store, so it is the only genuinely yours rather than estimated. A third-party index samples a large set of searches and reports where your pages appeared, useful because it also covers sites you do not own. Sondavo's website keyword checker at sondavo.com/website-keywords does the second job with no account and no card: enter a domain, yours or a rival's, and it returns the keywords that domain appears for with positions and monthly volumes. Use both. Search Console tells you what happened on your store, the index tells you what the landscape around it looks like.

    Because Magento generates them at scale and, by default, they are perfectly crawlable. Every filter combination on a category page can produce a distinct URL with parameters for colour, size, price band and manufacturer, and a catalogue with a handful of attributes produces thousands. Left alone, Google crawls them, treats near-identical pages as competitors for the same query, and spends crawl budget on combinations nobody searches for. The fix is a policy rather than a switch: canonical tags on filtered pages pointing at the clean category URL, a robots.txt rule for the parameter patterns you never want crawled, and a sitemap listing only clean canonical URLs. Check all three, because Magento's defaults, an extension and a theme can each quietly override the others.

    You cannot know without asking it repeatedly, the way a customer would. Asking once tells you almost nothing, because assistants vary their answers and because a UK shopper can get a different answer from a US shopper. What works is building a list of the real questions your market asks, putting them to the assistants on a schedule, and recording who was named and which pages were cited each time. Sondavo's AI visibility feature at sondavo.com/ai-visibility does that against ChatGPT, Claude, Gemini and Perplexity plus Google AI Overviews, stores the answers verbatim so you can read them, and reports the cited pages. UK location is used where the engines support it, which matters wherever a shopper's country changes the shortlist.

    X-robots-tag is an HTTP response header carrying the same instructions as a robots meta tag, noindex included, but it lives in the server response rather than the page source. That makes it invisible when you view source in a browser, which is why it causes such long-running mysteries. The classic Magento version is a staging site set to send x-robots-tag: noindex on every response so it stays out of search, and then a deployment, a copied vhost or a restored config carries that header into production. The store looks perfect, the HTML is clean, and Google quietly drops the pages. Any HTTP header checker shows it. Sondavo's free one is at sondavo.com/http-header-checker.

    It should not, and usually does not, but the risk is real enough to prepare for. What actually causes damage is mechanical: category and product URLs that change without a permanent redirect, redirect chains left by a partial URL rewrite, a sitemap still listing the old address structure, canonical tags pointing at the old domain, and staging noindex settings that travel with the code. Rankings can also wobble for a fortnight simply because Google recrawls a changed site, and that wobble is easy to mistake for damage. The protection is a baseline: record what you ranked for, what your key pages earned in clicks, and what your technical checks returned before the work starts.

    No. Sondavo works on any website and knows nothing about Magento specifically. It does not read your configuration, it will not tell you which admin setting produced a bad canonical tag, and it does not replace a developer who knows your store. It looks at your site the way a search engine or an AI assistant does, from outside, and reports what it finds in plain English. That external view catches a lot of Magento's characteristic faults, because they live in exactly the places a crawler looks: canonical tags on filtered pages, robots rules, sitemaps, redirects and response headers. Treat the findings as a diagnosis to hand to whoever maintains the store, not a fix in themselves.

    Yes, and it is often the faster route to a decision. Your own Search Console data tells you what you already win, but it cannot tell you what you are missing, because a query you have never ranked for produces no impressions and therefore no row. A keyword check on a rival's domain shows the searches they appear for and you do not, which is a direct list of category and content gaps. The same applies to AI answers: knowing an assistant names three rivals when asked about your product category is more actionable than any ranking number, because it also shows which pages it read to get there.

    Sources and further reading

    Upgrading, migrating, or just want to know where you stand?

    Run the free checks on your store, then talk to a UK engineer about the server side. We build the stack to your store's required versions and handle the redirect map on every migration we run.