SEO and AI SEO

SaaS Technical SEO Checklist: 25 Checks Before You Publish More Content

A person at a wooden desk holding a black mug and typing on a laptop that shows an On-Page SEO Dashboard with a score, organic traffic, keyword rankings, a traffic chart and a top issues list

SaaS technical SEO decides whether the content you already paid for can be found at all. Before you commission another ten blog posts, check that search engines can crawl, render and index the pages you have. Technical SEO for SaaS has its own traps, and most of them come from how software companies build their sites.

This SaaS technical SEO checklist gives you 25 checks. We wrote each one the way a QA engineer writes a test case: what to check, how to test it, and a pass condition you can mark as pass or fail. Then you get a one-week audit plan and an order for fixing what fails.

Why SaaS Technical SEO Comes Before More Content

A SaaS marketing site is rarely one simple website. It is usually a mix of:

  • A JavaScript-heavy marketing site built on a framework that may ship empty HTML and fill it in the browser.
  • An app subdomain with login pages, signup flows and sometimes public share links that search engines find.
  • Docs and a changelog on a separate platform, often with its own robots.txt, sitemap and templates.
  • Pricing pages that change often, get A/B tested and sometimes exist in three versions at once.
  • Staging and preview environments that leak into the index when nobody locks them down.
  • Integration directories with filters that can create thousands of near-duplicate URLs.

Publishing more content on top of that is like adding test cases to a build that does not compile. If you are earlier in the journey, our SEO playbook for SaaS startups shows where technical work sits next to keywords and content.

Crawl and Index Checks (1 to 5)

#CheckHow to testPass condition
1robots.txt on every hostOpen /robots.txt on www, docs, app and blog hosts. Test key URLs in Search Console’s robots.txt report.No money page, CSS or JS file is disallowed. Each host has its own intended file.
2XML sitemap completenessCompare sitemap URLs against your list of published pages and the Search Console Pages report.Every indexable page is listed. No redirects, 404s or noindex URLs in the sitemap.
3noindex and canonical conflictsCrawl the site and compare robots meta, canonical tags and sitemap inclusion per URL.No page is both in the sitemap and noindex. Canonicals point to 200, indexable URLs.
4Staging and app subdomain leakageSearch site:staging.yourdomain.com and site:app.yourdomain.com. Open staging in a private window.Staging needs a login. Only intended app pages, such as the login page, appear in results.
5Parameter and faceted URLsClick filters in your integrations directory and note the URLs. Check which ones are indexed.Filter combinations canonicalize to a clean page or are not linked as crawlable URLs.

Two gotchas here. First, robots.txt applies per host, so a clean file on www says nothing about docs or app. Second, a page blocked in robots.txt cannot show Google its noindex tag. If you want a page out of the index, allow crawling and use noindex, as Google explains in its guide to blocking indexing.

Rendering Checks (6 to 8)

#CheckHow to testPass condition
6JavaScript rendering of key contentRun URL Inspection in Search Console and view the rendered HTML. Compare with view-source.H1, body copy, pricing and internal links appear in the rendered HTML.
7Lazy-loaded contentInspect the rendered HTML for tabs, accordions and below-the-fold sections.Content you want ranked is in the DOM without a scroll or click.
8Client-side routingCheck that navigation uses real <a href> links and that each view has its own URL.No content views behind #fragments or onclick handlers. Every view returns a 200 on direct load.

Google renders JavaScript, but its JavaScript SEO basics still say links must be <a> elements with an href, and that single-page apps should use the History API instead of fragments.

Site Architecture Checks (9 to 12)

#CheckHow to testPass condition
9Internal links and orphan pagesCompare sitemap URLs with URLs found by a crawl that starts at the homepage.Every sitemap URL is reachable through at least one internal link.
10Broken links and redirect chainsScan key templates with the free Page Pulse Link Checker, then follow redirected links.No broken internal links. Internal links point to the final URL, not through a chain.
11URL structureList URL patterns for blog, docs, integrations, comparison and pricing pages.Short, lowercase, readable URLs with one consistent pattern per page type and one trailing slash rule.
12BreadcrumbsCheck visible breadcrumbs on blog, docs and integration pages.Breadcrumbs match the real hierarchy and every level is a working link.

Page Pulse is a free Chrome extension. It checks every link on the page you are viewing and marks each one as working, broken, redirected or unable to verify. It checks one page at a time, so point it at your templates: homepage, pricing, a docs page, a blog post and the integrations hub.

Performance Checks (13 to 15)

#CheckHow to testPass condition
13Core Web Vitals (LCP, INP, CLS)Open the Core Web Vitals report in Search Console and PageSpeed Insights field data for key templates.At the 75th percentile: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less.
14Image formats and sizingInspect hero and screenshot images on top pages.Modern formats such as WebP or AVIF, sized to display, with width and height set.
15Third-party scriptsList every tag in your tag manager and page source.Each script has an owner and a reason. Non-essential scripts load after the main content.

The thresholds in check 13 come from Google’s Web Vitals guidance on web.dev, which also says to measure the 75th percentile of page loads, segmented across mobile and desktop.

Structured Data Checks (16 to 18)

#CheckHow to testPass condition
16Organization markupValidate the homepage in the Schema Markup Validator.One Organization entity with name, url, logo and sameAs profiles. No errors.
17SoftwareApplication markupValidate product and pricing pages. Compare marked-up facts with the visible page.Name, category and offers match what a visitor sees. No ratings you cannot show on the page.
18BreadcrumbList and FAQPageRun the Rich Results Test on a blog, docs and integration page.BreadcrumbList matches visible breadcrumbs. Any FAQPage markup matches visible questions.

A note on FAQPage. Google’s documentation changelog says FAQ rich results stopped appearing in Google Search from May 7, 2026, and Google removed the FAQ rich result documentation in June 2026. Keep FAQ content if it helps readers, but do not plan traffic around an FAQ rich result.

International, AI Crawler and Docs Checks (19 to 23)

#CheckHow to testPass condition
19hreflang, if you have localized pagesCheck each language version’s hreflang tags or sitemap entries.Every version lists itself and its alternates, and the links are reciprocal. Skip if you publish in one language.
20AI crawler rulesRead robots.txt for GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot and PerplexityBot.Each rule is a decision someone made, written down, not a copied template.
21Named group precedenceFor every named user-agent group, confirm it repeats the * rules it still needs.No named group accidentally opens paths that * blocks.
22llms.txt (optional)If you publish one, open /llms.txt and check its links.Optional. If present, links resolve and describe current pages.
23Docs and changelog subdomainsCheck robots.txt, sitemap, canonicals and Search Console property for docs and changelog hosts.Docs are indexable, in a sitemap, link back to the main site, and old versions canonicalize to current ones.

Check 21 catches teams out. RFC 9309 says a crawler obeys the group that matches its name, and falls back to the * group only if no matching group exists. Google’s robots.txt documentation adds that user-agent specific groups and the global group are not combined. So in this file, GPTBot may crawl /app/:

User-agent: *
Disallow: /app/
User-agent: GPTBot
Disallow: /pricing-tests/

Know which bot does what. OpenAI says GPTBot crawls for model training and OAI-SearchBot surfaces sites in ChatGPT search. Anthropic separates ClaudeBot for training from Claude-SearchBot for search. Perplexity says PerplexityBot surfaces sites in its search results. Blocking a training bot is a business choice. Blocking a search bot by accident is a defect.

On llms.txt, Google’s changelog says these files are not needed for Google Search and will not help or hurt rankings, but it is fine to keep one for other services.

Security Checks (24 and 25)

#CheckHow to testPass condition
24HTTPS and HSTSRequest http:// and non-www versions of key URLs. Check response headers for Strict-Transport-Security.Every variant redirects in one hop to the HTTPS canonical host. HSTS header present.
25Mixed contentOpen key pages with the browser console showing and look for mixed content warnings.No HTTP images, scripts or iframes on HTTPS pages.

How to Run a SaaS Site Audit in a Week

A focused SaaS site audit fits in five working days if you test by template, not by URL.

  • Day 1: Inventory and links. Export your sitemap, the Search Console Pages report and a list of page templates. Run Page Pulse on one page per template and log every broken or redirected link.
  • Day 2: Crawl and index. Run checks 1 to 5. Test robots.txt on every host and search for staging and app URLs in the index.
  • Day 3: Rendering and architecture. Run checks 6 to 12 with URL Inspection and a crawler. List orphan pages.
  • Day 4: Performance and structured data. Run checks 13 to 18 on your top templates, starting with pricing and the homepage.
  • Day 5: AI crawlers, docs and security. Run checks 19 to 25. Then write the defect list: check number, URL, owner, priority and the pass condition that failed.

What to Fix First

PriorityFailuresWhy first
P1: blocks indexingChecks 1, 3, 4, 6, 24, and any search bot blocked by accidentPages that cannot be crawled, rendered or trusted cannot rank, whatever the content.
P2: wastes crawling or splits signalsChecks 2, 5, 9, 10, 21, 23Duplicates, orphans and chains spread attention across the wrong URLs.
P3: experienceChecks 7, 8, 13, 14, 15, 25Slow or unstable pages frustrate visitors, most of all on pricing and signup pages.
P4: enhancementsChecks 11, 12, 16, 17, 18, 19, 20, 22Useful once the basics pass. Change URL structure only with redirects planned.

Printable SaaS Technical SEO Checklist

  1. robots.txt is correct on every host
  2. Sitemap lists every indexable page and nothing else
  3. No noindex or canonical conflicts
  4. Staging is locked; app subdomain shows only intended pages
  5. Faceted and parameter URLs are controlled
  6. Key content appears in rendered HTML
  7. Lazy-loaded content is in the DOM
  8. Routing uses real links and real URLs
  9. No orphan pages
  10. No broken links or redirect chains
  11. One consistent URL pattern per page type
  12. Breadcrumbs match the hierarchy
  13. LCP, INP and CLS pass at the 75th percentile
  14. Images in modern formats with dimensions set
  15. Every third-party script has an owner
  16. Organization markup is valid
  17. SoftwareApplication markup matches the page
  18. BreadcrumbList and FAQPage match visible content
  19. hreflang is reciprocal, if used
  20. AI crawler rules are deliberate
  21. Named robots groups repeat the rules they need
  22. llms.txt is current, if used
  23. Docs and changelog are indexable and linked
  24. HTTPS everywhere with HSTS
  25. No mixed content

A Real Example From Our Technical SEO Work

Our technical SEO case study covers an IT services company rather than a SaaS product, but the foundation problems were the same ones this checklist tests. The site had no GA4 or Search Console connected, no structured data, thin internal linking and no process for submitting new pages.

Over a five-month engagement starting in June 2025, we reworked 60 pages at 12 a month, added 3 internal links per page, rolled out Article, FAQ, Breadcrumb and Local Business schema, and submitted every updated page to Google Search Console and Bing within 24 hours. It also added 75 backlinks from DA 20-plus domains and made 9 articles AEO-ready, with no new content produced.

Frequently Asked Questions

What is SaaS technical SEO?

SaaS technical SEO is the work that makes a software company’s site crawlable, renderable and indexable: robots.txt and sitemaps across every subdomain, JavaScript rendering, internal links, Core Web Vitals, structured data, AI crawler rules and HTTPS.

How long does a SaaS site audit take?

A focused audit fits in five working days if you test one page per template instead of every URL. The last day goes to AI crawlers, docs, security and a prioritized fix list.

Should a SaaS company block GPTBot and ClaudeBot?

It depends on what you want. OpenAI says GPTBot crawls for model training while OAI-SearchBot surfaces sites in ChatGPT search. Anthropic separates ClaudeBot for training from Claude-SearchBot for search. You can block training bots and still allow search bots, but write each rule on purpose, because a named user-agent group ignores the rules in the * group.

Do we still need FAQPage structured data?

Do not add it for a Google rich result. Google’s documentation changelog says FAQ rich results stopped appearing in Google Search from May 7, 2026. If you keep FAQPage markup, make sure it matches questions and answers that are visible on the page.

Use the free Page Pulse Link Checker Chrome extension from QualiPulse. It checks every link on the page you are viewing, marks each one as working, broken, redirected or unable to verify, and exports results to CSV or JSON.

Next Step: Technical SEO for SaaS With QualiPulse

If the failures pile up, you do not need more content yet. You need the defect list fixed in the right order.

Our AI SEO services cover technical SEO for SaaS sites along with AI search visibility, reviewed by a team with a QA background. Read our technical SEO and GEO FAQ for how we work, or send us your domain on the contact page and we will tell you which checks fail first.

Fix the foundation, then publish.

Send us your domain. We will run the checks that matter most for your site and tell you what to fix before your next round of content.