SaaS SEO auditFull SEO

A full SEO audit of a SaaS site: feature and pricing pages, docs, blog and what to keep out of search

Usually ready in 15 minutesRevisions includedQuality check
Packages
Payment protectionDetails
  • Revisions within the package are free.
  • If you do not respond within 3 days of delivery, the work is accepted automatically.

The money is reserved when you pay and released only once you accept the work.

A full SEO audit of a SaaS site: feature and pricing pages, docs, blog and what to keep out of search

Example result

Example for the Standard package

SEO audit: website of a regional plumbing company

Summary

AreaScoreMain issue
Indexing and crawlingNeeds work38 blog tags pages indexed, thin content
Technical healthFairMobile load time 4.8 s on service pages
On-pageNeeds work11 of 18 service pages share near-identical titles
Local signalsWeakTown pages are copies with the town name swapped
ContentFairBlog traffic is high, but posts do not link to services

Findings (excerpt)

1. Duplicate and weak titles (high priority)

11 service pages use the pattern "Plumbing Services | Northgate". Searchers and search engines cannot tell "boiler repair" from "drain unblocking".

PageCurrent titleSuggested title
/boiler-repairPlumbing Services, NorthgateBoiler Repair in [City], Same-Day Callout, Northgate
/blocked-drainsPlumbing Services, NorthgateBlocked Drains Cleared in [City] from £89, Northgate

2. Town pages are near duplicates (high priority)

The 7 town pages are 94% identical text. Each needs at least 250 words unique to that town: areas covered, typical jobs there, travel time, a local customer review.

3. Slow service pages on mobile (medium)

Hero images average 1.9 MB. Compressing to WebP and setting width to 1,200 px would bring load time to about 2.5 s.

4. Blog does not pass value to services (medium)

The top 10 posts get 62% of organic visits, but only 2 of them link to a service page. "Why is my boiler losing pressure?" alone gets about 1,100 visits a month and links nowhere.

5. Tag pages indexed (low)

38 /tag/ pages with 1–3 posts each. Set them to noindex.

Prioritised action plan

#ActionEffortImpactWho
1Rewrite titles and meta descriptions for 18 service pages1 dayHighContent
2Write unique content for 7 town pages3–4 daysHighContent
3Add service links to the top 10 blog posts2 hoursMediumContent
4Compress hero images2 hoursMediumDeveloper
5Noindex tag pages, update sitemap1 hourLowDeveloper

Re-check: crawl again 6 weeks after items 1–3 are live and compare impressions for "[service] + [town]" queries.

Client: Northgate Plumbing & Heating, 11 engineers, serving one city and 6 nearby towns Site: 214 pages: home, 18 service pages, 7 town pages, 160 blog posts, contact and legal pages Goal: more calls from local searches such as "boiler repair [town]"

The client and all details are made up.

About this service

A SaaS site is rarely one site: there is the marketing site, a blog, a help centre or docs, often on different subdomains or platforms, and login and signup pages that search engines should not waste time on. We audit them together from the public side: indexing and robots.txt, sitemaps, subdomains versus folders, duplicate docs versions, whether key text is in the page code or only appears after scripts run, titles, headings and structured data, and how feature, pricing, integration and comparison pages are linked. You get a report and a plan ordered by priority, written so your developers can work through it. You send the main domain and the sections that matter. We never log in to your product, change the site or promise positions.

What is included

  • What you getA report on the SEO problems found across your site, blog and docs, covering as many pages as your package has, and a plan ordered by priority that names the pages and templates each fix applies to. You get it on the order page to read or download.
  • Site, blog and docsSubdomains and folders checked together
  • Out of searchLogin, signup and app pages
  • Pages built by scriptsIs the key text in the page code?
  • Product pagesFeatures, pricing, integrations, comparisons
  • Docs versionsDuplicates and canonical pages

How it works

  1. 1
    BriefYou send the domain and key sections
  2. 2
    AuditWe go through site, blog and docs
  3. 3
    Report and planYou get findings and a plan by priority
  4. 4
    RevisionsYou ask questions or for more detail within your package

What we need from you

The main domain and the addresses of the blog, help centre or docs, what the product does and for whom, the pages that matter most (pricing, features, integrations), what the site is built on, and the markets you target.

We will ask you:

  • Which domains and sections should be audited?
  • What is the site built on?
  • Which pages matter most?
  • Who will make the changes?

Compare packages

PackagesBasicSite up to 50 pages$35StandardSite up to 500 pages$71PremiumSite up to 5,000 pages$134
Deadline2 days3 days5 days
Revisions122
Site typeSaaS siteSaaS siteSaaS site
Order BasicOrder StandardOrder Premium

Payment protection

You pay when you order, but the money is released only for accepted work.

  • Fixed priceThe package price does not change after you pay.
  • The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
  • Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
  • Free revisionsAsk for changes within your brief as many times as the package allows.
  • Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
  • Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
How it works →

Questions and answers

Do you need a test account in the product?

No. Search engines only see the public pages, and that is what we audit. We never log in to the product.

Our site is built with a JavaScript framework. Is that a problem?

Not by itself. We check whether titles, text and links are in the page code search engines receive, and the plan says what to change if they are not.

Will the audit bring signups?

It shows what holds the site back in search and in what order to fix it. Positions and signups depend on much more, so we promise neither.

Do you need logins to my site or analytics?

No. The audit works from the public pages of the site, so a link is enough. If you have figures from Google Search Console or analytics, describe them in the brief and we take them into account.

Will you make the changes on the site?

No, we do not access sites. The audit is a report with a plan; you or your developer make the changes by following it step by step.

Did not find your answer?

Packages