I will do a complete technical SEO audit with a prioritized Screaming Frog fix list
About this gig
I will do a complete technical SEO audit of your site using Screaming Frog and hand you a prioritized, plain-English fix list your team can actually ship — no fluff, no generic checklist.
What you get
A technical SEO audit is only useful if it ends in action, so everything I deliver is built around what to fix, in what order, and why it matters. Here is exactly what lands in your inbox:
- A full crawl of your site run in Screaming Frog SEO Spider, configured for your CMS, JavaScript rendering needs, and crawl scope (subdomains, parameters, and staging excluded or included as agreed).
- A prioritized fix list delivered as a spreadsheet — every issue tagged Critical / High / Medium / Low, with the affected URL count, the likely impact, and the recommended fix written so a developer or content editor can act without guessing.
- Indexability and crawl analysis: orphan pages, redirect chains and loops, 4xx/5xx errors, canonical conflicts, noindex/nofollow mistakes, robots.txt and meta robots issues, and pages blocked from crawling that shouldn't be.
- Site architecture and internal linking findings: crawl depth problems, pages buried too deep, weak internal linking to money pages, and broken or looping internal links.
- On-page technical signals: missing, duplicate, or truncated title tags and meta descriptions, H1 problems, thin or duplicate content patterns, and image alt-text gaps surfaced by the crawl.
- Directives and structured signals: hreflang errors (if you run international/multilingual), pagination handling, canonical correctness, and XML sitemap coverage vs. what's actually crawlable.
- Core Web Vitals and page experience flags pulled in via the PageSpeed Insights integration, so slow templates and layout-shift offenders show up alongside everything else.
- A short written summary (PDF or Doc) that translates the spreadsheet into a narrative: your three to five biggest wins, what to do first, and what can wait.
Every finding is specific to your URLs. You won't get a recycled "best practices" PDF — you get a list that names your actual pages and your actual problems.
Plans
| Feature | Basic | Standard | Premium |
|---|---|---|---|
| Pages crawled (up to) | 500 | 5,000 | 25,000+ |
| Screaming Frog full crawl | Yes | Yes | Yes |
| Prioritized fix-list spreadsheet | Yes | Yes | Yes |
| Indexability & crawl-error analysis | Yes | Yes | Yes |
| Internal linking & architecture review | — | Yes | Yes |
| Core Web Vitals / page-experience flags | — | Yes | Yes |
| Hreflang / international SEO checks | — | — | Yes |
| Written summary report | Brief notes | Yes | Yes + loom-style walkthrough |
| Revisions | 1 | 2 | 2 |
| Delivery (business days) | 3 | 5 | 7 |
If your site is larger than the Premium tier, message me first — large crawls are absolutely doable, I just need to scope the crawl settings and timeline correctly.
How it works
- You send access and context. I need your domain, a heads-up on the CMS/platform, and ideally read-only access to Google Search Console and analytics. If you have a staging site or specific sections to include or exclude, tell me up front.
- I configure the crawl. This is the step most "audits" skip. I set user-agent, rendering mode (text vs. JavaScript), crawl limits, parameter handling, and integrations (PageSpeed, Search Console, analytics) so the data reflects how search engines actually see your site.
- I run the crawl and let it complete fully. Big sites take time; I don't truncate the crawl just to deliver faster, because a partial crawl produces a misleading fix list.
- I analyze and prioritize. I work through indexability, architecture, directives, on-page signals, and performance flags, then rank every issue by impact and effort so you're not staring at 4,000 undifferentiated rows.
- I deliver the spreadsheet and summary, and walk you through the top priorities.
- You get your revision(s). If a fix needs more detail or a finding needs clarifying, send it back and I'll refine it within your tier's revision allowance.
Why choose this
Plenty of tools will export thousands of "issues" and call it an audit. The hard part — the part I do — is judgment: separating the issues that genuinely move rankings and crawl efficiency from the noise that looks scary but doesn't matter. I prioritize ruthlessly so your team spends its limited engineering time on the fixes that pay off.
I'm also honest about scope. This is a technical audit: crawlability, indexability, site structure, directives, and the technical on-page signals Screaming Frog surfaces. It is not a keyword-research project, a backlink audit, a content-writing engagement, or a guarantee of ranking positions — no honest SEO can promise rankings. I'll flag where those other workstreams would help, but I won't pad this deliverable with things it isn't.
Finally, I write for humans. The fix list is plain English a developer can hand to a sprint and a marketer can understand. No jargon dumps.
Who it's for / use cases
- Site owners and marketing teams who suspect technical issues are holding back organic traffic but don't know where to start.
- Agencies that need a white-label-friendly technical crawl and fix list to support a client engagement.
- Developers about to do a redesign, migration, or replatform who want a pre- or post-launch technical baseline.
- E-commerce stores drowning in faceted-navigation, parameter, and duplicate-content problems.
- Anyone who ran a free online "SEO checker", got a scary score, and now wants a real, prioritized plan.
FAQ
Q: Do you fix the issues for me, or just identify them? This gig is the audit and prioritized fix list — diagnosis and a clear action plan. I document each fix so your developer can implement it. If you'd like me to implement changes too, message me and we can scope that as separate work.
Q: Will this guarantee I rank #1 on Google? No, and anyone who promises that is not being straight with you. Technical SEO removes the obstacles that stop search engines from crawling and indexing your site properly. It's a foundation that makes your other SEO efforts work — not a magic ranking switch.
Q: How many pages can you crawl? That depends on your tier — up to 500, 5,000, or 25,000+ pages. Larger sites are fine; just message me first so I can scope the crawl configuration and delivery time correctly.
Q: What access do you need from me? Your domain at minimum. Ideally read-only Google Search Console and analytics access too, which makes the audit far more accurate (orphan-page detection, real performance data). I'll tell you exactly what to share, and you can revoke access after delivery.
Q: My site uses heavy JavaScript / is a single-page app. Can you still audit it? Yes. I configure Screaming Frog's JavaScript rendering mode so the crawl reflects what gets rendered and indexed, rather than just the raw HTML. Let me know your framework so I set rendering up correctly.
Q: What format is the deliverable? A spreadsheet (Google Sheets or Excel) for the prioritized fix list, plus a written summary as a Doc or PDF. On the Premium tier you also get a recorded walkthrough of the findings.
Q: How long does it take? Three to seven business days depending on tier and site size. Very large crawls can take longer; I'll give you a firm timeline once I've scoped your site.
Q: Can I ask follow-up questions after delivery? Absolutely. Each tier includes revisions, and I'm happy to clarify any finding so your team knows exactly what to do. Honest, useful answers — not upsell pressure.
Reviews★4.6(5)
- @mintworks★★★★★5
The Screaming Frog crawl surfaced broken redirects and duplicate title tags I had no clue existed, and the prioritized fix list made it obvious what to handle first.
- @eli_a★★★★★4
Honest no-fluff technical SEO review, the findings on my orphaned pages and missing meta descriptions were spot on and easy to action.
- @mason_media★★★★★5
Really thorough technical audit, everything was ranked by impact so I could hand the high-priority items straight to my developer.
- @thedevco★★★★★4
Clear audit and a well-ordered fix list. Would've liked a bit more detail on a couple of the smaller items, but the important issues were all covered.
- @works7★★★★★5
Found redirect chains, crawl errors and missing canonicals my last guy completely missed, and the list told me exactly which fixes mattered this week versus later.