Investigate
Inspect crawl access, templates, canonicals, schema, internal links, performance, and platform behaviour.
Technical SEO · AEO · Implementation
Technical SEO audit by
Technical SEO audit by
someone who codes the fix.
Technical audit for WordPress, Webflow, Shopify, WooCommerce, SaaS, and custom websites. Crawlability, indexation, structured data, canonical structure, Core Web Vitals, and a prioritized fix list written by a senior developer.
Verified Upwork skills: Technical SEO · On-Page SEO · almost 15 years web delivery · 12 years WordPress
What this is
A technical SEO audit is a prioritized implementation plan for the issues stopping a business website from being crawled, understood, trusted, or converted.
For example, a service page marked noindex or carrying a conflicting canonical can disappear from the route search engines are meant to evaluate. The audit identifies the observed issue, explains the business risk, specifies the implementation owner, and verifies the intended public URL after the fix. It does not substitute a generic score for that evidence.
Prioritize
Order observed issues by business risk, implementation dependency, and likely search impact.
Implement or hand off
Provide stack-specific steps, or implement the agreed fixes in the existing platform.
Verify
Recheck the intended URL, visible markup, key templates, and the completed route after the work.
Check one page first for a fast observable triage, or run the free audit for a broader report and PDF.
The Gap
Most SEO audits are written for the wrong audience.
Agency audits are written for SEO managers — full of vague recommendations like "improve site speed" or "fix duplicate content" without telling the developer how. Mine are written for the dev who'll implement them. Or I implement them myself.
What most SEO audits give you
- —62-page PDF with no priority order
- —Recommendations like "improve speed" with no implementation steps
- —Generic advice with no platform or implementation context
- —Zero help with implementation — "your dev team will handle it"
- —A ongoing support plan pitch attached to every recommendation
What I deliver
- +32 specific checks, prioritized by impact × effort
- +Implementation steps in Liquid / PHP / your stack
- +Platform-specific quirks across WordPress, Webflow, Shopify, WooCommerce, and custom builds
- +Platform-specific checks for templates, taxonomies, rendering, and routing
- +Optional: I implement the top 10 fixes myself, no ongoing support
The 32-Point Checklist
What I check, every audit.
Crawl & Indexation
robots.txt, XML sitemap accuracy, noindex audit, internal linking depth, orphaned pages, blocked resources, JS rendering parity for googlebot.
10 checks
On-Page & Structured Data
Title/meta uniqueness, H1 hierarchy, canonical tags, Schema.org markup (Product, Review, FAQ, Organization), Open Graph & Twitter Cards, image alt & lazy-loading.
12 checks
Performance & Site Health
Core Web Vitals (CrUX + Lighthouse), TTFB, mobile usability, broken links, redirect chains, SSL config, HTTP/2 + HTTP/3 negotiation.
10 checks
Request a review
Evidence first. Fix order before implementation.
Send the site and platform. We will review the current crawl, search, answer-engine, and conversion risks, then reply with the right audit or implementation path.
- ✓ 32-point technical audit for the current platform
- ✓ Prioritized fix list with implementation steps
- ✓ 25-min Loom walkthrough by a senior dev
- ✓ Optional: hands-on implementation, scope-led
FAQs
Audit questions, answered.
How is this different from an automated audit? +
Automated tools can detect patterns, but they cannot reliably decide which issue matters most to this business, buyer path, or codebase. The review connects technical evidence to business impact, fix ownership, and implementation steps for the actual stack.
How long does the audit take? +
Timing depends on site size, rendering complexity, and access. After the initial URL review, we confirm the scope and delivery sequence before work starts.
Do you fix the issues you find? +
Optionally, yes. Implementation of the top fixes is scope-led, scoped to what's needed. You're not required to use me — the audit stands on its own and any developer can implement from it.
Will an audit guarantee ranking gains? +
No. An audit can identify and prioritize barriers, but search performance also depends on demand, competition, content quality, authority, implementation, and measurement. We state what the evidence supports and avoid ranking guarantees.
Can the review include content and AEO gaps? +
Yes. The core is technical, but the report can also flag thin answers, unclear entities, weak service-page coverage, missing proof, schema mismatches, and internal-link gaps that affect search and answer-engine visibility.
Audit to implementation
The report should end with fixes someone can ship.
Lofts Studio connects technical SEO audit findings to crawl access, search appearance, AEO readiness, internal links, conversion paths, and the production work needed to make the report useful.