Technical SEO Audit for SaaS: Your Step-by-Step Checklist

How to Do a Technical SEO Audit of Your SaaS Website With Semrush

SaaS websites break in sneaky ways. A marketing site on one stack, docs on another, the app on a third subdomain.

Google sees all of it. So do AI crawlers now.

A proper technical SEO audit catches the crawl traps, broken redirects and JavaScript gaps quietly bleeding your signups.

Semrush Site Audit is one of the fastest ways to find them. It checks over 140 on-page and technical issues, renders JavaScript, and now scores your AI search readiness too.

We'll walk you through the full Semrush Site Audit setup for a SaaS site, the settings that matter, the reports worth your time, and the fixes that move rankings.

Technical SEO Audit for SaaS: A Quick Overview

  • Semrush Site Audit crawls your site and flags technical SEO issues as errors, warnings and notices, then rolls them into a Site Health score from 0% to 100%.
  • It performs over 140 checks, including crawlability, HTTPS, hreflang, internal linking, Core Web Vitals, structured data and AI search readiness.
  • For SaaS sites, turn on JS rendering (Guru or Business plan), crawl each subdomain deliberately, ignore tracking parameters, and keep app and login areas out of the crawl.
  • Fix errors first, then warnings, starting with pages that drive trials and demos.
  • Check the AI Search Health score and the Blocked from AI Search widget to see if robots.txt blocks AI crawlers.
  • A free Semrush account audits only 100 pages. Pro allows 100,000 pages per month, Guru 300,000 and Business 1,000,000.

Mapping Your SaaS Site Before the First Crawl

Here's where most SaaS audits go wrong. People type the root domain, hit start, and get a confusing mix of blog, docs, app and help center pages.

Map your site first. Ten minutes here saves hours later.

Typical SaaS Site Sections

  • Marketing site: Homepage, features, pricing, use cases, comparisons, integrations.
  • Blog: Sometimes on /blog/, sometimes on blog. subdomain.
  • Docs and knowledge base: Often on docs. or help. subdomains, sometimes a separate platform.
  • App: Usually app. subdomain. Login walls, user data, not meant for search.
  • Programmatic pages: Integration pages, templates, alternatives, location pages.
  • Localised versions: Language folders or subdomains with hreflang.
  • Staging environments: Should never be indexable.

Decide What Each Audit Covers

Semrush lets you audit a domain, subdomain or subfolder. You can also toggle “Crawl all subdomains” on a domain.

  • Audit the marketing site and blog together if they share a domain.
  • Audit docs separately. Docs are often huge and need their own crawl budget.
  • Skip the app entirely, unless public pages live there.
  • Audit staging only with credentials, to catch issues before launch.

Step by Step Semrush Site Audit Setup for a SaaS Website

Step 1. Create the Project and Open Site Audit

  • Create a project for your domain in Semrush.
  • Your first project starts a Site Audit campaign automatically. Later projects need manual setup.
  • Open Site Audit and click the setup button to configure the crawl.

Step 2. Set the Scope and Page Limit

  • Enter the domain, subdomain or subfolder you mapped earlier.
  • Decide on “Crawl all subdomains.” For SaaS, usually off, so app subdomains stay out.
  • Set a page limit per audit within your plan, up to 20,000 on Pro and Guru or 100,000 on Business.

Step 3. Choose the Crawl Source

Crawl SourceHow It WorksWhen to Use It on SaaS
WebsiteFollows links from the homepage, breadth firstFinding orphan pages and checking internal linking
Robots.txt sitemapCrawls only URLs in the sitemap linked from robots.txtChecking that the sitemap holds only clean, indexable URLs
Sitemap by URLCrawls one sitemap you enterAuditing one section, like docs or blog
Import URLs from fileCrawls a .csv or .txt file, one URL per linePriority pages only, like pricing and feature pages, to save crawl budget

Website crawling finds pages reachable from the homepage, not necessarily the most important ones. So for big SaaS sites, we often add a second audit with a file of money pages.

Step 4. Configure Crawler Settings

  • User agent: SiteAuditBot Mobile is the default. Desktop is also available. A newer option, OpenAI-Search, checks crawlability for OpenAI's search bot.
  • Crawl delay: Minimum delay is the fastest, around one second between pages. Pick “1 URL per 2 seconds” or “Respect robots.txt” if your server struggles.
  • JS rendering: Turn it on for JavaScript heavy sites. Requires Guru or Business.

Googlebot Desktop and Mobile are no longer selectable as user agents. Older campaigns already using Googlebot keep it until you change the setting.

Step 5. Set Allow and Disallow Rules

  • Allow only the paths you want, such as /blog/ or /integrations/.
  • Disallow paths like /login/, /signup/ or /account/.
  • Always include the trailing slash. Without it, /docs also matches /docs-old.

Step 6. Remove URL Parameters

SaaS sites collect parameters from campaigns, pricing toggles and in app links.

  • Add parameters like utm_source, utm_medium, ref, plan or billing.
  • Semrush then crawls each URL once instead of every variant.

Step 7. Bypass Restrictions Where Needed

  • Robots.txt bypass: Upload Semrush's verification file to your root to crawl pages blocked by robots.txt or meta robots.
  • Credentials: Enter a username and password for staging or protected sites.
  • Web Bot Auth signature: For hosts that block unknown bots. Needs a Signature Agent URL, Signature Input string and Signature value.

Step 8. Schedule and Start

  • Pick weekly on a set day, daily, or once.
  • Click Start Site Audit. Crawl time depends on size and crawl delay.
  • Connect Google Analytics afterwards, so issues on top viewed pages stand out.
SettingOur SaaS DefaultWhy
ScopeMarketing domain, subdomains offKeeps app pages out
Crawl sourceWebsite, plus a sitemap auditFinds orphans and checks sitemap hygiene
User agentSiteAuditBot MobileMatches mobile first indexing
Crawl delayMinimum, unless the server strugglesFaster audits
JS renderingOnMost SaaS marketing sites rely on JavaScript
DisallowLogin, signup, account and app pathsNo value in auditing private pages
Ignored parametersUTM, ref, plan and billing togglesStops duplicate URL noise
ScheduleWeeklyCatches release regressions

Reading the Site Audit Overview Like a SaaS Marketer

The crawl is done. Now the dashboard shows a lot. Here's what deserves your attention.

Site Health Score

  • A percentage from 0% to 100%, based on errors and warnings found relative to checks performed.
  • Errors weigh more than warnings.
  • Treat the score as a trend line, not a grade. Fixing one error on your pricing page matters more than ten notices on old blog posts.

Errors, Warnings and Notices

  • Errors: Shown in red. The most severe issues. Fix first.
  • Warnings: Shown in orange. Medium severity.
  • Notices: Lower priority items worth reviewing.

Crawled Pages Breakdown

Shows pages that are healthy, broken, have issues, redirect, or were blocked. On SaaS sites, a big “redirect” slice usually points to old feature URLs and rebrands.

Top Issues and the Issues Tab

  • Top Issues ranks problems by priority and the number of affected pages.
  • The Issues tab shows every issue, with “Why and how to fix it” guidance.
  • Filter the Issues tab by category, including the AI Search category.

Thematic Reports That Matter Most for SaaS Websites

Semrush groups checks into eight thematic reports. Some matter far more for SaaS than others.

Thematic ReportWhat It CoversSaaS Focus
Robots.txtChanges to robots.txt and crawl issuesAccidental blocks after a deploy
CrawlabilityCrawl depth, status codes, sitemap vs crawled pagesDeep feature pages and sitemap junk
HTTPS ImplementationCertificates, server support, site architectureMixed content on old landing pages
International SEOHreflang tags in page HTMLLocalised pricing and feature pages
PerformancePage size, redirects, compression, caching, minificationHeavy marketing pages with many scripts
Internal LinkingClick depth, orphan pages, link distribution, Internal LinkRankOrphaned integration and comparison pages
MarkupsStructured data, valid or invalidFAQ, product and organisation markup
Core Web VitalsLCP, CLS and Total Blocking Time via Lighthouse, on 10 pagesHomepage and pricing page speed

Crawlability on SaaS Sites

  • Semrush suggests keeping crawl depth under three clicks from the homepage.
  • Check the sitemap vs crawled pages comparison. Pages in the sitemap but not crawled may be orphaned or blocked.
  • Watch for 4xx errors on old pricing plans and retired features.

Performance and Core Web Vitals

  • The Performance report tracks average HTML load speed and recommends loading pages in under one second.
  • Core Web Vitals uses Lighthouse to measure Largest Contentful Paint, Cumulative Layout Shift and Total Blocking Time.
  • The CWV report analyses 10 pages. Pick your homepage, pricing, top feature pages and top blog posts.

Internal Linking

  • Spot orphan pages with zero internal links.
  • Check which pages pass the most Internal LinkRank. Ideally, pricing and core feature pages sit near the top.
  • Integration and template pages often end up orphaned after launches. Link them from hub pages.

Structured Data Checks in the Markups Report

Schema helps search engines and AI systems understand what your product is. The Markups report shows what you have and what's broken.

  • Valid vs invalid: The report grades each item, so broken markup is easy to spot.
  • Markup by type: See which schema types exist and on how many pages.
  • Item level detail: Open individual items to see which fields fail.

Schema Types Worth Having on a SaaS Site

  • Organization on the homepage, with logo and official profiles.
  • SoftwareApplication on product or pricing pages, with category, operating system and offers.
  • BreadcrumbList on docs, blog and integration pages.
  • Article or BlogPosting on blog posts, with author and dates.
  • FAQPage where real FAQs exist. Google now shows FAQ rich results mainly for authoritative government and health sites, so treat it as context for machines rather than a SERP feature.

Keep schema honest. Prices, ratings and features in markup must match what users see on the page.

JavaScript Rendering Checks With the JS Impact Report

This is the report SaaS teams need most, and use least.

JS Impact compares your pages before and after JavaScript executes. It shows what changes once rendering finishes.

  • Pages impacted: How many audited pages needed JavaScript rendering to show their final content.
  • Parameters changed after rendering: Which elements changed, such as titles, descriptions and links.
  • Guide view: An overview of where elements changed or went empty.
  • Table view: Filter by parameter, for example changed titles or links.

Semrush renders with Chromium, a stack similar to Googlebot's. So results should closely reflect what Google sees.

What to Look For on SaaS Pages

  • Titles or meta descriptions that only appear after rendering.
  • Internal links injected by JavaScript, which crawlers may find late or miss.
  • Pricing tables that render client side and show nothing in raw HTML.
  • Canonical tags that change after rendering.

SaaSGoodies Reality Check:Many AI crawlers fetch raw HTML and don't execute JavaScript the way Google does. If your key copy only exists after rendering, AI answers may never see it. Server side rendering or static generation for marketing pages solves both problems.

AI Search Health and AI Crawler Access Checks

This is the newest part of Site Audit, and the one most SaaS sites ignore.

AI assistants now answer “best tool for X” questions directly. If AI crawlers can't read your site, you're out of the answer.

AI Search Health Score

  • A dashboard score estimating how ready your site is for AI driven search.
  • It weighs AI search checks, AI bot access through robots.txt, and technical readiness like schema, crawlable navigation, internal links and llms.txt.
  • Filter the Issues tab by “AI Search” to see specific problems and fixes.

Checks Inside the AI Search Category

  • Llms.txt not found. Flags sites without an llms.txt file.
  • Links with non-descriptive anchor text.
  • Links with no anchor text.
  • Pages with only one incoming internal link.

The AI Search category is available on all Semrush subscription levels.

Blocked From AI Search Widget

Shows how many audited pages robots.txt blocks for specific AI bots. Here are the eight bots Semrush checks.

BotType
ChatGPT-UserOn demand fetcher
Perplexity-UserOn demand fetcher
Claude-UserOn demand fetcher
OAI-SearchBotAI search crawler
PerplexityBotAI search crawler
Claude-SearchBotAI search crawler
GooglebotAI search crawler
Google-ExtendedAI search crawler and training token

To allow a bot, add an Allow: / rule under its user agent in robots.txt. If you use a firewall or bot protection, allow those user agents there too.

Want to see your site the way ChatGPT search does? Set the crawler user agent to OpenAI-Search and compare the results.

Semrush Pricing in 2026 for Technical SEO Work

Semrush now sells its SEO features as the SEO Toolkit, or bundled inside Semrush One with AI visibility features.

PlanMonthly PriceSite Audit LevelBest For
SEO Toolkit Pro$139.95Pro limits, no JS renderingSmall static marketing sites
SEO Toolkit Guru$249.95Guru limits, JS renderingMost SaaS marketing sites
SEO Toolkit Business$499.95Business limits, JS rendering, AMPLarge SaaS sites with big docs
Semrush One Starter$199Includes ProSEO plus AI visibility on a budget
Semrush One Pro+$299Includes GuruGrowing SaaS teams
Semrush One Advanced$549Includes BusinessLarger teams and agencies

Annual billing lowers the effective monthly price. The AI Visibility Toolkit also sells separately for $99 per month.

Semrush Logo

Semrush Discount: Unlock Free 14-Day Pro Trial

Claim the Semrush Free 14-day Pro Trial and explore technical SEO audits, site analysis, keyword research, and powerful SEO tools.

Sitemap and Indexability Checks Every SaaS Audit Needs

Your XML sitemap is a promise to Google. “These pages matter, please index them.”

On many SaaS sites, that promise is full of junk.

  • Redirected URLs in the sitemap: Old feature pages that now redirect waste crawl attention.
  • Noindex pages in the sitemap: A mixed signal. Either index the page or drop it from the sitemap.
  • Broken pages in the sitemap: Retired plans and deleted docs often linger for months.
  • Missing money pages: New integration or comparison pages that never got added.
  • Several sitemaps, one forgotten: Docs platforms and blog tools often generate their own sitemaps.

Here's the quick test we use. Set up one audit with the Website crawl source and one with the Robots.txt sitemap source. Then compare.

  • Pages found by the crawl but missing from the sitemap need adding.
  • Pages in the sitemap but never reached by the crawl are likely orphans. Link them internally.

The Crawlability report's sitemap vs crawled pages comparison does a lot of this work for you.

Canonical Tags and Duplicate Content on SaaS Sites

Duplicate content on SaaS sites rarely comes from copying. It comes from templates and parameters.

Where Duplicates Come From

  • Monthly and annual pricing toggles that create separate URLs.
  • Campaign parameters left inside internal links.
  • Trailing slash and case variants, like /Pricing and /pricing/.
  • www and bare domain versions, or HTTP and HTTPS versions both live.
  • Programmatic templates with the same title and meta description on every page.
  • Docs versions, where v1, v2 and v3 pages carry near identical content.

How to Clean Them Up

  • Give every indexable page a self referencing canonical.
  • Point parameter and variant URLs to the clean version.
  • Force one protocol and one hostname with 301 redirects.
  • Write unique titles and meta descriptions for programmatic pages, even short ones.
  • Canonical old docs versions to the current version, unless users still search for old ones.

After fixing, rerun the audit and check that duplicate title and description counts drop. If they don't, the canonical may only exist after JavaScript rendering. The JS Impact report will show it.

Redirects and Status Codes After Rebrands and Migrations

SaaS companies rename features, merge plans and rebrand more than almost anyone. Every change leaves redirects behind.

  • Redirect chains: Old URL to newer URL to newest URL. Point every old URL straight to the final one.
  • Redirect loops: Two URLs pointing to each other. These break crawling completely.
  • Temporary redirects left in place: A 302 used for a permanent move. Switch to 301.
  • Internal links to redirected URLs: Update navigation and footer links to final URLs.
  • 5xx errors: Server errors on marketing pages during deploys or traffic spikes. Check hosting and caching.

Planning a domain move or a CMS migration? Audit the old site before the move and save the export. After launch, audit again and compare. Any page that lost its redirect shows up fast.

SaaS Specific Technical SEO Issues and How to Fix Them

Generic audit guides miss these. They show up on almost every SaaS site we review.

SaaS IssueHow It Shows in SemrushFix
App or login pages indexableCrawled pages from app paths, duplicate titlesNoindex and block app areas, disallow in the audit
Staging site publicDuplicate content across domainsPassword protect and noindex staging
Old plan and feature URLs4xx errors and broken internal links301 redirect to current equivalents
Redirect chains after rebrandsRedirect chains and loopsPoint every old URL straight to the final URL
Pricing table rendered by JavaScriptJS Impact shows changed or missing contentRender pricing server side
Thin programmatic pagesLow word count, duplicate meta descriptionsUnique copy per integration or template page
Orphaned integration pagesOrphan pages in Internal LinkingLink from an integrations hub
Docs on a separate platformMissing canonicals, duplicate titlesSelf canonicals and unique titles per doc
UTM parameters in internal linksDuplicate URLs with parametersClean internal links, ignore parameters in the audit
Broken hreflang on localised pagesInternational SEO errorsCorrect codes and return tags

Pricing Pages Deserve Special Care

Your pricing page is often the highest intent page on the whole site.

  • Make sure plan names and prices exist in raw HTML.
  • Avoid parameter driven versions for monthly and annual toggles being indexed separately.
  • Check speed and layout shift on mobile.

Prioritising Fixes by Business Impact

A big SaaS audit can show thousands of issues. You can't fix them all this sprint.

Prioritise by severity and by page value.

PrioritySeverityPage TypeExample
1ErrorPricing, signup, demo, core feature pagesBroken pricing page, noindex on feature page
2ErrorBlog and docs with trafficBroken links on top blog posts
3WarningMoney pagesSlow load, missing structured data
4WarningSupporting pagesDuplicate meta descriptions on docs
5NoticeAny pagePages with only one internal link
  • Connect Google Analytics so Semrush highlights issues on your top viewed pages.
  • Work through Top Issues on the Overview tab for quick wins.
  • Use the “How to fix” guidance in the Issues tab when briefing developers.

Tracking Progress After Fixes Ship

  • Rerun the audit after a fix deploys.
  • Progress report: An interactive graph showing how issue counts change across audits.
  • Compare crawls: See what changed between two audits, useful after big releases.
  • Scheduled audits: Weekly crawls catch regressions from new deploys.
  • Position Tracking: Set up tracking once Site Health improves, and add notes each time you ship a fix to connect changes with rankings.

What Good Progress Looks Like

  • Error count trending down across three or more audits.
  • Zero errors on pricing, signup and core feature pages.
  • Fewer pages blocked from AI search, unless blocking is intentional.
  • Crawl depth for money pages within three clicks of the homepage.
  • New issues caught within a week of each release, not months later.

SaaSGoodies Take: We schedule audits the day after the usual release day. If a deploy breaks robots.txt or canonicals, we know within a day, not a quarter.

Troubleshooting a Failed Semrush Site Audit

  • “Auditing domain has failed.” Usually your server blocks SiteAuditBot. Allow the bot in your firewall or download the failure log for your developer.
  • Very few pages crawled. Check robots.txt, the page limit, and allow or disallow rules.
  • Host blocks unknown bots. Use the Web Bot Auth signature option.
  • Staging blocked. Add credentials in the bypass step.
  • Content missing in results. Turn on JS rendering, if your plan allows it.
  • Server load spikes. Slow the crawl to one URL per two seconds or respect robots.txt crawl delay.

Final Verdict on Semrush Technical SEO Audits for SaaS

SaaS websites change every sprint. New features, new pages, new scripts, new subdomains.

Each change can quietly break crawling, rendering or indexing.

A Semrush Site Audit catches those breaks before they cost you signups. Map your site, configure the crawl properly, read the right thematic reports, and fix issues by business impact.

Then keep the audit on a schedule. Technical SEO isn't a project you finish. It's hygiene you keep.

Shearing is Caring:-

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *