SaaS marketing sites are often built by the same engineers who build the product, on the same frameworks. That brings specific problems that a generic audit misses.
Rendering
Google can render JavaScript, but its documentation describes rendering as a separate step after crawling, and blocked resources or script errors can leave content out of what gets indexed. Key marketing pages (home, pricing, features, comparisons, integrations) should be server-rendered, statically generated or prerendered, with titles, canonicals and body copy present in the initial HTML. We test with Search Console's URL Inspection and compare rendered and raw source. Sites that run a headless front end get the same checks.
App, login and staging URLs
Sign-in pages, password reset flows, shared dashboards, staging environments and preview deployments leak into the index more often than most teams realise. We set noindex, robots rules, authentication or canonicals as each case requires and remove what should never have been crawled.
Subdomains, subfolders and sitemaps
A blog on one subdomain, docs on another and the app on a third splits internal linking and makes reporting messy. We document the trade-offs, plan any move with 301 redirects, and set up separate XML sitemaps for marketing, docs and integration sections so crawl issues are easy to isolate.
Speed on script-heavy pages
Chat widgets, product tours, A/B testing scripts and analytics tags pile up on SaaS sites. We trace which third-party scripts slow Core Web Vitals and work with speed optimization to defer or remove them.