Crawl and delivery
Can crawlers reach the site, follow its redirects and read its robots rules and sitemaps? We also show how much of the site we managed to cover.
FREE ASTRO SEO CHECKER
Check the SEO your Astro site actually shipped.
An Astro project can look right in the repo and still ship broken titles, missing canonicals or pages search engines can't reach. Paste in the live URL and we'll show you exactly what's there, with evidence for every finding.
Loading the checker...
We couldn't start the checker. Try reloading the page, or download the Astro repository checklist and use it in your project.
SCAN IN PROGRESS
Reading the deployed site.
Preparing the site...
YOUR REPORT
Scan complete
0Important issues
0Site-wide warnings
0Page-specific warnings
0Manual checks
Not detectedFramework
Findings
View all checks and their status
WHAT GETS CHECKED
Astro gives you a head start. What ships is what counts.
Astro can ship complete HTML with little or no client JavaScript. That does not automatically give every route the right title, canonical, sitemap entry, image handling or crawl path. We check the deployed output, not the packages in your repo.
Titles and metadata
Does each page ship a title, description, canonical and social tags in a clean, readable head?
Content and links
Are headings in order, links crawlable and meaningful content present in the initial HTML? We also check whether each page can be indexed.
Images and structured data
Do images declare their alt treatment and dimensions? Are loading priorities sensible, and can search engines read the structured data?
Patterns across pages
Are titles, descriptions or canonical targets repeating where they shouldn't? Do similar pages behave consistently?
Astro fingerprints
We look for Astro's fingerprints in the deployed HTML and assets, then report which framework the evidence supports.
HOW TO READ THE REPORT
Not every finding means something is broken.
Every finding comes with the evidence behind it and the pages it affects. Its label tells you whether we found a real conflict, spotted something worth reviewing, or reached a point where only you have enough context to decide.
Something is clearly wrong
Either we couldn't read a page, or two parts of the site are sending search engines in opposite directions. A page listed in your sitemap but marked noindex is a good example: one says "come and look", the other says "keep this out of search".
Fix these first.
Not broken, but worth a closer look
Search engines can still make sense of the site, but you may be making their job harder or giving them less to work with. One internal link that redirects is not a big deal. Forty pages sharing the same description is a pattern worth fixing.
Worth fixing, but not an emergency.
Only you can say whether it matters
We can see what the browser receives, but not what each part of the page is for. A search box that only renders in the browser may be perfectly fine. A pricing table built the same way may hide the most important content on the page. The output looks similar, but the context changes the answer.
Read the evidence, then make the call.
The numbers only cover what we scanned.
If your site has 200 pages or fewer, the numbers cover the whole site. If it is larger, we spread the sample across its sections instead of taking the first 200 URLs we find. When the same issue appears across much of the sample, it probably affects more pages too. The report still counts only what we actually scanned.
Not every check can run on every scan.
Open the full checks list to see what happened to every check. Pass means it ran and found no issue. Not applicable means there was nothing relevant to test. Not checked means we did not have enough data to run it. Only pass confirms a clean result.
HONEST LIMITS
A live URL shows what shipped, not what produced it.
We can inspect the HTML, headers, redirects, robots rules and sitemap your live site returns. We cannot see the Astro config, route logic, integrations or components behind them.
That is where the repository checklist takes over. It covers the other half of the audit: the routes, configuration and components a public scan cannot see. Use it yourself or hand it to your developer or coding agent.
Download the Astro repository checklistWe can make these fixes for you.
If the report exposes a deeper structural problem, we take it from deployed evidence to a tested production fix. Book a call and we will walk through your report together.