Building With Astro? 5 SEO Tools for Static Websites

For a static Astro website, start with tools that check what you build, what you deploy and what Google actually sees. You don't need five subscriptions to do that.

Astro prerenders pages by default, but static HTML can still contain broken links, incorrect canonicals or the wrong sitemap URLs. A successful build won't catch every one of those problems.

These five SEO tools cover different parts of that workflow. I'm a co-founder of Screpy, which is included below. This comparison uses official documentation and pricing checked on October 31, 2026, without claiming a hands-on benchmark.

Which Astro SEO tool solves which problem?

These tools overlap in places, but they aren't replacements for one another. Choose based on the question you're trying to answer.

Prices retain their displayed currencies and billing periods. The paid options don't replace Google's own indexing evidence, and a sitemap generator doesn't audit the pages it lists.

1. @astrojs/sitemap

The official Astro sitemap integration handles a narrow, useful job: generating sitemap files from the routes your project builds.

Install it from your Astro project with:

npx astro add sitemap

Review the resulting configuration and set site to your production origin. A configured build produces sitemap-index.xml and sitemap-0.xml in the output directory. Check the deployed files too; a correct local file is no help if the host serves an older version.

This fits a prerendered blog or documentation site. It also covers dynamic routes generated through getStaticPaths(). Dynamic routes served on demand need separate handling because the integration cannot automatically enumerate them.

Use it for discovery, then verify the URLs it publishes. It won't find a broken link in your article or tell you which pages Google indexed. Google's sitemap guidance explicitly separates URL discovery from guaranteed crawling and indexing.

2. Screaming Frog SEO Spider

Screaming Frog SEO Spider is useful when you want a focused desktop crawl of the deployed site. It finds broken links and redirects, and lets you review titles, descriptions and other page signals together.

For a small static site, the free version's 500-URL crawl limit may be enough. Start with the HTML your server returns. JavaScript rendering becomes relevant only if important content or navigation depends on browser scripts.

The paid licence is currently listed at £199 per year. Saving crawls, scheduling, advanced configuration and JavaScript rendering are among the restricted features in the free edition.

Choose it for a deliberate audit you run yourself. If you want a shared place to revisit findings over time, compare that desktop workflow with a project-based service before buying.

3. Screpy

Screpy's SEO crawler gives you a project workspace for inspecting pages, response codes, metadata, canonicals and internal links. For an Astro site, it works with the public website; you don't need a native Astro plugin to crawl the deployed HTML.

This is useful when the question changes from “what's broken in this release?” to “where do we keep track of technical findings?” You can trace an internal destination back to its source pages instead of treating a broken URL as an isolated error.

Pro's regular annual price is $192, billed for the full year upfront. It includes five projects and 5,000 crawl pages per project. Welcome offers can change checkout pricing; subscriptions renew automatically, and the seven-day trial converts to paid unless canceled.

For a static Astro build, leave JavaScript rendering off when the required content is already in the HTML. Fixes still belong in your project or hosting configuration; the crawler doesn't rewrite your Astro files.

4. Google Search Console

Google Search Console answers a question your own crawler cannot settle: what information does Google have about your site?

It's a free service for reviewing search performance, indexing problems and related reports. You need access to the appropriate property to inspect its URLs.

After publishing an Astro page, use URL Inspection to check the indexed version and, separately, test the live URL. These are different views. The live test can help investigate the current page, but it doesn't establish that Google's index already contains that version.

For example, after correcting a canonical in your layout, the deployed HTML may be right while Google's stored information still reflects an earlier crawl. Don't keep changing the template just because those two views haven't caught up with each other.

Use Search Console alongside your crawler. The crawler helps investigate the site you serve; Search Console provides Google's indexing and search-performance context.

5. PageSpeed Insights

PageSpeed Insights is the free URL-level check to use when a deployed page feels slow or you want to investigate performance before adding more scripts and media.

Test representative templates, not just your homepage. A plain landing page and an article with large images or embeds can behave very differently, even when both come from the same Astro project.

Google's PageSpeed documentation distinguishes two kinds of evidence: Lighthouse lab diagnostics and real-user data collected over a trailing 28-day period. Lab results help investigate a page now. Field data describes recorded user experience.

New or low-traffic pages may not have enough field samples. Check whether the report shows page-level data, origin-level data or no field data at all. Missing data isn't a passing result.

Use the diagnostics to decide what to investigate. A performance score doesn't tell you whether your sitemap is correct or whether Google indexed the page.

Check one release from build to Google

Suppose you rename a post from /blog/old-guide/ to /blog/new-guide/. This is an illustrative release check, not a tested deployment.

A sitemap containing the new URL would be only one piece of the evidence. Your navigation might still link to the old address, or the new page might declare the old canonical.

Give each finding an action. A wrong canonical belongs in the layout or its data. An outdated internal link needs a link update; a missing redirect needs attention in your routing or hosting rules. A poor performance diagnostic needs investigation of that template. A live/indexed mismatch needs checking before you assume the build is broken again.

For a small Astro site, start with the sitemap integration, Search Console, PageSpeed Insights and a free desktop crawl. Add a paid workflow when you need more capacity, advanced controls or a shared project workspace. That gives each tool a reason to be there, rather than another subscription to maintain.