In brief
You’ll know what broke, what it affects, and what to fix first, with evidence you can point to and a change list your developer can implement without guesswork.
I’ll run a technical SEO audit that isolates the blocker, ranks fixes by impact, and writes each change in developer-ready terms. Next, you’ll pick a start date and I’ll send the access list.
I start by crawling the site the way search engines do, then I check what actually made it into the index and why. I compare rendered pages to source HTML to catch JavaScript gaps, review logs to see real bot behaviour, and turn the findings into a short, ordered fix list your developer can ship.
A bit about me
I’m Minseo Park, a Technical SEO auditor. I do audits for sites where rankings move after code changes, templates, or a platform switch, and the business needs a clear answer fast. I focus on crawl, indexation, rendering, and performance because those are the parts that decide whether content can compete at all.
I’m the person you hire when you want the technical truth, not a long checklist. I don’t hide priorities inside a 70-page report. I call out the one or two blockers first, show the proof, then give you a fix order that matches how developers work: what to change, where to change it, and what to verify after release.
Recent work
Here are three recent technical SEO audits where the goal was to find the blocker and hand developers a fix order they could ship.
Portfolio
JS rendering audit. Organic landing pages weren’t indexing consistently because key content only appeared after client-side rendering. I documented the HTML vs rendered diff, flagged the templates involved, and gave a test plan to confirm Google could see the content.
Indexation and canonicals review. A template update introduced self-referencing canonicals on filtered pages and cross-canonicals on key categories. I mapped the canonical patterns, identified the affected URL sets, and wrote exact rules for canonicals, pagination, and parameter handling.
Log-file bot budget review. Googlebot spent most of its crawl on faceted URLs and thin internal search pages, while new product pages were discovered late. I broke down bot hits by directory and status code, then recommended crawl controls and internal linking changes.
“The audit told our developer exactly what to change, in the right order.”
In-house marketer, a B2B exporter site
Audit summary
A short write-up of the main blocker, what it’s affecting, and the fastest path to stabilise crawl, indexation, and rankings after the change.
PRIORITISED FIX LIST
A ranked list of fixes with severity, expected impact, and dependencies, so your developer knows what to ship first and what can wait.
DEVELOPER-READY NOTES
Per issue: where it shows up, how to reproduce it, the evidence (URLs, screenshots, log examples), and the exact change to make in templates, headers, or rules.
Crawl and index coverage findings
Crawl export findings plus index checks that show what’s being discovered, what’s excluded, and which patterns are causing waste or accidental blocking.
RENDERING AND JS PARITY FINDINGS
A set of checks that compares source HTML to rendered output, including specific templates and elements that fail to render for bots.
CWV AND PERFORMANCE BOTTLENECK LIST
A list of the slowdowns that are dragging Core Web Vitals, tied to page types and causes like script weight, render-blocking assets, and caching behaviour.
Pricing
Choose based on how much site surface area I need to verify beyond the first blocker and how much evidence your developer needs to ship fixes confidently.
Priced items
Get started
If you want me to start isolating the blocker and turning it into a fix order, sign here and I’ll lock in the first available slot.
1. Sign the proposal and I’ll send the booking invoice for 25%. 2. Share the access items from my checklist so I can start the crawl and checks. 3. I’ll confirm the start date, then begin the technical SEO audit.
Signature
Fee summary
What do you need access to, and is any of it risky?
I’ll ask for read-only access where possible: Search Console, analytics, a crawlable environment, and log files or a log export. Nothing I do changes your site. I don’t need production write access to run the audit.
WILL THIS TELL MY DEVELOPER EXACTLY WHAT TO CHANGE?
Yes. Each issue comes with the affected patterns, proof, and a specific change request. If a fix depends on your stack, I’ll give options, then note what to verify after your developer ships it.
How long until you can point to the main issue?
I usually identify the primary blocker in the first 2 to 3 working days once I have access, because crawl data and index checks surface hard blocks fast. The rest of the time goes into confirming edge cases and writing the fix notes.
CAN YOU SANITY-CHECK A PLANNED MIGRATION BEFORE WE PUSH IT?
Yes. I can run a migration and replatforming risk audit on the plan, redirects, canonicals, sitemaps, and staging behaviour. You’ll get a pre-launch punch list and a launch-day verification checklist.
Booking and payment
To book, you’ll pay 25% when the proposal is signed. The remaining 75% is due when I hand over the finished technical SEO audit. Invoices are payable within 14 days of the invoice date.
Access and safety. I’ll ask for read-only access where possible, such as Search Console, analytics, a crawlable environment, and log files or a log export. Nothing I do changes your site, and I don’t need production write access to run the audit.
What counts as done. The work is complete when I deliver the audit summary, prioritised fix list, and developer-ready notes, plus the crawl, index coverage, rendering, and performance findings described in this proposal.
Changes to scope. If I find a material issue that isn’t covered by the agreed package, I’ll tell you what it is, what extra access or time it needs, and the added cost before I continue past the original scope.
Client inputs
My timeline depends on timely access and the right exports. If access or files are delayed, I’ll pause the work and restart when everything is available, without guessing or filling gaps.
Confidentiality. I’ll treat your accounts, exports, and findings as confidential. I’ll only share them with people you authorise, and I won’t use your site or data as an example publicly without your written OK.
Retesting fixes. If your developer ships changes after delivery, I can verify the fixes against the original evidence and checks. Retesting is a separate piece of work, priced after I see what changed and what needs re-crawling.
