An illustrative sample of how I turn technical SEO findings into implementation tasks. All example.com addresses and issues below are hypothetical; this is a work sample, not a client-results case study.
Restore indexing for a service page — P1
Affected URL: https://example.com/services/seo-audit/
Example issue: the page returns 200 and is linked internally, but carries noindex despite being intended for search.
Required change: remove noindex from the page settings and check X-Robots-Tag. Keep the page crawlable so search engines can read the updated directives. Use a self-referencing canonical.
Remove an unnecessary redirect step — P1
Example chain: /audit/ → /seo-check/ → /services/seo-audit/.
Required change: redirect /audit/ directly to /services/seo-audit/ with 301. Update internal links and the sitemap to the final 200 URL. Retain the intermediate redirect if that old address has links or traffic.
Fill missing page titles — P2
Affected URLs: https://example.com/services/seo-audit/ and https://example.com/services/technical-seo/.
Suggested titles: “SEO Audit & Developer Brief | Example” and “Technical SEO Services | Example”. Set one title element per page, using the correct page template.
Give different articles distinct titles — P2
Affected URLs: https://example.com/blog/canonical/ and https://example.com/blog/redirects/.
Replace the shared generic title with a title describing each article: “How to Set Up Canonical URLs | Example” and “How to Set Up 301 Redirects | Example”.
Deliverable format
For a real website, the report includes confirmed evidence, every affected URL, implementation instructions and priorities. The scope of the audit and any verification after implementation are agreed before work begins.
0 likes · 1 view · Nov 10, 2026
Demonstration of a technical SEO audit: affected URLs, indexing fixes, redirects and page-title requirements written as clear tasks for a developer.