SEO Audit Checklist for Custom Software and Automation

If Google can’t reliably crawl your service pages, it can’t rank them—and you’ll feel it as “SEO traffic” that never turns into qualified calls. For custom software, automation, and private AI firms, the most expensive SEO problems are usually boring ones: the wrong URL version indexed, a slow template across every revenue page, or core services buried where neither buyers nor Google look.

This checklist gives you a one-hour, evidence-first audit you can run without turning it into a week-long project. You’ll capture what’s broken, tie it to impact on rankings and leads, then sort fixes by Impact and Effort so your next steps are obvious.

  1. Crawl (10-15 min): Run a crawl with Screaming Frog SEO Spider (or Sitebulb) and export indexable URLs, status codes, canonicals, titles, and H1s.
  2. Verify (20-25 min): Cross-check crawl findings in Google Search Console (Indexing, Sitemaps, Manual actions) and a speed test in Google PageSpeed Insights.
  3. Score (10 min): Tag each finding with Impact and Effort using the grid below.
  4. Prioritize (10 min): Sort by High Impact first, then pick the smallest Effort items you can complete this week.
  • Impact: High (blocks crawling, indexing, rankings, or leads), Medium (hurts relevance or UX), Low (nice-to-have).
  • Effort: S (copy or simple CMS change), M (template or dev ticket), L (architecture, migration, or multi-sprint work).

Can Google Crawl and Index Your Pages? (Indexation Checklist)

Before you score anything else, confirm Google can actually see your pages. This part of the SEO audit checks whether your service pages, case studies, and resources can be crawled and indexed, then whether Google chose the right version of each URL.

Indexation Checklist in Google Search Console

  • Coverage Reality Check: In Google Search Console, review Pages (Indexing). Look for “Crawled, currently not indexed,” “Discovered, currently not indexed,” and “Duplicate, Google chose different canonical.” Export examples so your dev team can reproduce patterns.
  • URL Inspection Spot Tests: Inspect 5 to 10 money pages (core services, highest-value case studies). Confirm “URL is on Google,” confirm the Canonical Google selected, and check “Page fetch” details for blocked resources.
  • XML Sitemap Hygiene: In Sitemaps, submit a single canonical sitemap index if possible. Your sitemap should include only indexable 200-status canonical URLs. Remove redirected URLs, parameter URLs, and staging domains. Validate counts: sitemap “Submitted” should roughly match “Indexed” for key sections, not differ by thousands.
  • robots.txt and Meta Robots: Verify robots.txt allows crawling of important paths (for example, /services/, /case-studies/, /resources/). Then check templates for accidental noindex on production pages, a common failure after site rebuilds. Use Google’s robots.txt documentation for reference: Google: robots.txt.
  • Canonical Tag Sanity: Every indexable page should self-canonicalize unless you intentionally consolidate duplicates. Watch for canonicals pointing to the homepage, HTTP versions, or a different service page. That mistake quietly kills rankings.
  • Duplicate and Parameter URLs: Identify query-string variants (UTMs, filters, session IDs) and near-duplicates (trailing slash, uppercase, print pages). Fix with consistent internal links, canonical tags, and, where appropriate, redirects. For parameter handling guidance, use: Google: Consolidate Duplicate URLs.

Score each issue with Impact (High, Medium, Low) based on how many revenue pages it affects, and Effort (Small, Medium, Large) based on whether it needs a template fix, a redirect map, or a deeper CMS change.

Is Your Site Fast and Stable Enough to Rank? (Technical Performance)

Technical performance issues usually land as Medium or High Impact because they hit every revenue page at once. For an SEO audit checklist, treat speed and stability as a gate: if the page loads slowly or shifts around, Google sees weaker UX signals and buyers bounce before they read your proof.

  • Core Web Vitals (Impact: High, Effort: M-L): Check URL-level data in Google PageSpeed Insights. Prioritize pages that fail LCP (slow hero section), INP (laggy interactions), or CLS (layout shift from late-loading fonts, cookie banners, or embeds).
  • Mobile Usability (Impact: High, Effort: S-M): In Google Search Console, open the “Mobile Usability” report. Fix tap targets, viewport issues, and horizontal scrolling. Many B2B sites break on mobile when sticky headers and chat widgets stack.
  • HTTPS And Mixed Content (Impact: High, Effort: S-M): Confirm every template forces HTTPS and that no images, scripts, or iframes load over HTTP. Mixed content warnings can block assets and hurt rendering.
  • Broken Links And 4xx/5xx Errors (Impact: Medium-High, Effort: S-M): Use Screaming Frog to export broken internal links and server errors. Fix internal links first, then investigate recurring 5xx spikes with your host or Cloudflare logs.
  • Redirect Chains (Impact: Medium, Effort: S-M): In Screaming Frog, filter “Redirect Chains.” Replace chains with a single 301 to the final URL, especially for service pages that attract links.
  • Image Optimization (Impact: Medium, Effort: S-M): Serve WebP or AVIF, compress oversized PNGs, and set width and height attributes to reduce CLS. Watch for 2-5 MB hero images on case studies.
  • JS/CSS Rendering Blockers (Impact: High, Effort: M-L): Confirm key content and internal links render without client-side JavaScript. If navigation or service copy loads after JS, Google may index a thin version of the page. Check “View Source” vs rendered DOM in Chrome DevTools.

Quick Triage For B2B Service Sites (SEO)

If you only have 10 minutes, test your top 5 service pages and top 5 case studies in PageSpeed Insights, then open the “Diagnostics” section. Create dev tickets for the repeat offenders (largest contentful paint element, unused JavaScript, render-blocking resources) and score them High Impact because one fix often improves dozens of URLs.

Does Your Site Architecture Match How Buyers Search? (B2B IA)

Page speed fixes help, but architecture decides whether Google and buyers understand what you do. In a B2B SEO audit, information architecture (IA) is where custom software and automation firms lose rankings: they bury core services, mix unrelated offerings on one page, and leave case studies orphaned with no internal links.

  • Service Taxonomy Matches Search Language (Impact/Effort): List your top revenue services as buyers phrase them (for example: “custom software development,” “business process automation,” “system integration,” “private AI”). Each needs a dedicated landing page. Score High Impact if you currently rely on a single “Services” page. Effort is usually M (new pages plus navigation updates).
  • Navigation Makes Money Pages Obvious: Your primary nav should expose 4 to 7 core services, plus Case Studies and Resources. If a buyer needs two clicks and a guess to find “Automation,” you have an IA problem. Score Medium to High Impact, Effort S to M depending on your CMS.
  • One Intent Per Page: Avoid “Custom Software + Automation + AI” pages that try to rank for everything. Split into separate pages and connect them with contextual links. Score High Impact when Search Console shows impressions across unrelated queries for the same URL.
  • Internal Linking Between Services, Case Studies, and Resources: Every service page should link to 2 to 4 relevant case studies and 1 to 2 deep resources (guides, checklists). Every case study should link back to the service page that explains the work. Score High Impact if your case studies have no “Related Services” links.
  • Fix Missing Or Thin Service Landing Pages: If you sell “API integration” or “workflow automation” but only mention it in a blog post, you create thin topical coverage. Create a landing page with use cases, industries, and proof. Score High Impact, Effort M.

Quick IA Tests Using Crawl Data

In Screaming Frog, sort by “Crawl Depth” and filter to /services/ and /case-studies/. If key service pages sit at depth 4+, reduce clicks through nav changes and hub pages. Then review internal link counts. A core service page with fewer than 20 internal inlinks usually lacks site-wide support and struggles in a technical SEO checklist review.

On-Page SEO Checklist for Service and Case Study Pages

If a core service page has fewer than 20 internal inlinks, Google also tends to see weak on-page signals. This part of the SEO audit checklist checks whether each service and case study page clearly targets one query intent, says it in the HTML, and supports it with structured data.

  • Title Tags (Impact: High, Effort: S): Put the primary keyword and a qualifier in the first 60-ish characters. Example: “Custom Software Development for Logistics | JAMD Technologies.” Avoid repeating the same title across multiple services.
  • Meta Descriptions (Impact: Medium, Effort: S): Write a specific promise plus proof. Mention a concrete outcome like “reduce manual processing time” or “integrate NetSuite and Salesforce,” then add a next step (book a call, request an estimate).
  • H1 and Heading Structure (Impact: High, Effort: S-M): Use one H1 that matches the page topic. Use H2s for deliverables, industries, process, and FAQs. Case studies should include H2s for “Problem,” “Solution,” “Results,” and “Stack” so Google can extract entities.
  • Keyword-to-Page Mapping (Impact: High, Effort: M): Map one primary query to one URL. If “workflow automation” and “business process automation” compete across two service pages, consolidate or differentiate by audience (for example, “automation for finance ops” vs “automation for manufacturing”). Track the mapping in a simple Google Sheet.
  • Image Alt Text (Impact: Low-Medium, Effort: S): Use alt text for meaning, not keywords. Example: “Before-and-after dashboard showing invoice approvals reduced from 5 days to 1 day.” Skip alt text on decorative icons.

Baseline Schema Markup for B2B SEO

  • Organization schema (Impact: Medium, Effort: S-M): Add to the site template with legal name, logo, and sameAs links (LinkedIn, YouTube if used). Use Google’s reference for structure: Organization structured data.
  • Service schema (Impact: Medium, Effort: S-M): Add to each service page with serviceType, areaServed (if applicable), and provider as your Organization.
  • FAQPage schema (Impact: Medium, Effort: S): Use only when the FAQs are visible on the page and answer real buyer objections (budget range, timeline, security, integrations).
  • Article schema (Impact: Low-Medium, Effort: S): Apply to resources and guides, not service pages. Include author and dateModified so updates register.

Validate schema with Google’s Rich Results Test, then score fixes by how many revenue pages share the same template.

The Contrarian Check: Are You Ranking for the Wrong Leads?

Schema can be perfect and you can still fail the SEO audit if the site attracts the wrong searches. “Vanity SEO” happens when a custom software or automation firm ranks for broad, low-buying-intent queries (or unrelated ones), then wonders why leads are small, price-sensitive, or unqualified.

  • Search Console intent check (Impact: High, Effort: S): In Google Search Console, open Performance and filter by your top service URLs. Scan queries for “free,” “template,” “jobs,” “salary,” “definition,” “tutorial,” “examples,” “tools,” or competitor product names. Those terms can be fine for a blog, but they are a red flag when they drive impressions to a service page.
  • Title tag promise vs page reality (Impact: High, Effort: S-M): If the title says “Business Process Automation Services” but the page reads like a generic agency overview, Google will test you on broader queries and buyers will bounce. Rewrite the first 150-250 words to match a specific buyer problem (for example, “automate invoice approvals in NetSuite” or “reduce manual QA with test automation”).
  • Positioning is too vague to qualify leads (Impact: High, Effort: S-M): Phrases like “we build new solutions” qualify nobody. Replace them with constraints and fit statements: industries you know (healthcare operations, logistics, manufacturing), stacks you ship (Python, .NET, Node.js, AWS, Azure), and delivery model (discovery sprint, fixed-scope, retainer).
  • Thin proof signals “student project,” not “vendor” (Impact: High, Effort: M): Add concrete evidence near the top: named clients (with permission), before-and-after metrics, screenshots, architecture diagrams, security notes (SOC 2 alignment, HIPAA considerations), and a short “What We Actually Built” section.

Fix Intent Match With Differentiation and FAQs (SEO)

  1. Map each service page to one buying-intent query cluster: “custom ERP integration,” “warehouse automation,” “private AI for internal search,” not “software solutions.”
  2. Add 6 to 10 buyer FAQs (Effort: S): Answer pricing models, timeline ranges, security approach, data ownership, and what you need from the client. Use the questions you hear on discovery calls.
  3. Route informational queries to resources: Keep “how to automate X” terms on guides, then link to the relevant service page with a clear CTA.

Score this section High Impact when sales calls feel misqualified or Search Console shows irrelevant query patterns. Most fixes are Small to Medium effort copy and template updates.

What Tools Should You Use, and When Should You Get Help?

When calls feel misqualified, you need tools that connect queries to pages and pages to leads. A lean SEO audit stack gives you enough evidence to fix problems fast without turning the work into a software project.

Lean Tool Stack for a B2B SEO Audit Checklist

  • Google Search Console (Impact: High, Effort: S): Use it for indexation, query-to-page mismatch, and manual actions. The Pages report tells you what Google indexed. The Performance report shows which queries bring the wrong intent.
  • Google Analytics 4 (Impact: High, Effort: S-M): Use GA4 to confirm which landing pages create engaged sessions and which pages drive form submits or booked calls. If GA4 conversions are not set up, treat that as High Impact because you cannot prove SEO value.
  • Google PageSpeed Insights (Impact: High, Effort: S-M): Use it to triage Core Web Vitals on your top service pages and top case studies. Export repeat offenders (LCP element, render-blocking resources) into dev tickets.
  • Screaming Frog SEO Spider or Sitebulb (Impact: High, Effort: S): Use a crawler to find status codes, redirect chains, canonicals, duplicate titles, thin pages, and orphaned URLs. This is the fastest way to turn “we think” into a punch list.
  • Ahrefs or Semrush (Impact: Medium, Effort: S-M): Use one for backlink quality checks and competitor gap scanning. You are looking for which service pages earn links in your space and which topics competitors cover with dedicated landing pages.

If you keep this stack tight, you can re-run the technical SEO checklist monthly and spot regressions after releases.

Get help when the fix crosses team boundaries or risk rises. Bring in an experienced partner when you see High Impact issues with Large Effort (IA rebuilds, JavaScript rendering problems, migrations, widespread canonical mistakes), or when you need a keyword-to-page map that changes positioning and sales enablement copy.

JAMD Technologies offers an SEO + AI visibility audit that turns your findings into a practical roadmap: Impact (High/Medium/Low), Effort (S/M/L), owner (marketing or dev), and the exact evidence from Search Console, GA4, PageSpeed Insights, and crawl exports. If you want one next step today, pick your top 10 revenue URLs, run the crawl and PageSpeed tests, then schedule an audit review to turn the data into implementation tickets.