First-party case study · technical SEO · AI-search readiness
A first-party SEO case study on how I tightened daviddacruz.dev for agent search optimization, answer engine visibility, technical SEO hygiene, and clearer service conversion, with site-wide audit results before and after the work.
For this report, the audit score means the share of audited URLs with no blocking issues and no warnings in the site-wide scanner.
Executive summary
The reportable outcome is simple: 0 blocking issues in both full-site audits, 6 warnings on the older public audit cleaned down to 0 on the current preview audit, more crawlable pages, stronger internal links, and a clearer route from AI-search discovery into the services that sell.
100/100
preview audit score across 96 audited URLs
93/100
live-site audit score across 82 audited URLs
0
blocking issues in both full-site audits
10+
SEO and AEO surfaces added or strengthened
Report context
This page is not a representative example. It is the first-party record of what I changed on daviddacruz.dev to make the site structurally stronger for technical SEO, AI-mediated search, and service discovery.
The important point is not that one page was rewritten. The important point is that the site was tightened as a system: topic ownership, support pages, crawl resources, schema, metadata, internal links, and conversion paths all had to line up.
That is the type of work this service is meant to showcase. Not SEO theater. Not isolated recommendations. A cleaner public surface with measurable audit improvement and a stronger path from search visibility into commercial pages.
Audit snapshots
April 25, 2026
100/100
The local preview audit covered 96 URLs and came back with 0 blocking issues and 0 warnings. That is the cleanest view of the current shipped structure.
April 22, 2026
93/100
The public-domain audit of the live site covered 82 URLs. It also had 0 blocking issues, but still showed 6 metadata warnings at that point. Those warnings were one of the cleanup targets.
Before vs current state
Metric
Before
82 live URLs
Current
96 preview URLs
Why it matters
The public surface expanded while staying crawlable and structured.
Metric
Before
0
Current
0
Why it matters
The site stayed technically clean while the cluster grew.
Metric
Before
6
Current
0
Why it matters
Metadata and page-level hygiene improved from the public audit state.
Metric
Before
58
Current
87
Why it matters
The homepage now routes more aggressively into priority pages and proof surfaces.
Metric
Before
51
Current
58
Why it matters
The service layer is more connected to audit, comparison, cost, and case-study pages.
Metric
Before
175 chars
Current
137 chars
Why it matters
One of the warning-level metadata issues was corrected in the newer state.
What shipped
The site now has a dedicated parent page for agent search optimization instead of letting the topic exist as scattered mentions across blog posts and services. That created a cleaner commercial center of gravity.
I added and strengthened supporting pages for SaaS intent, audit intent, cost, consultant-vs-agency comparison, and related explanatory surfaces. The goal was not raw page count. It was intent separation and retrieval depth.
The site now presents a more deliberate crawler surface through llms.txt, llms-full.txt, sitemap.xml, news-sitemap.xml, robots.txt, feed.xml, and location.kml, alongside stronger page-type schema.
The audit work was not abstract. The public audit still showed long metadata on key pages. That cleanup work was part of the path from 6 warnings on the live audit to 0 warnings on the newer preview audit.
Older content now points more directly into the newer AI-search cluster, and top navigation surfaces route more clearly into the audit and proof pages. This matters because service pages perform better when support content reinforces them.
The implementation now exists as a tutorial, a first-party case study, service CTAs, and searchable support pages. That makes the SEO work itself part of the marketing system instead of leaving it hidden in the codebase.
Public proof assets
Parent page
/solutions/agent-search-optimizationPrimary commercial hub for the topic cluster.
Vertical child page
/solutions/agent-search-optimization-for-saasA more specific intent layer for SaaS buyers.
Service route
/services/ai-search-readiness-auditThe main audit offer this work now reinforces.
Cost page
/cost/agent-search-optimization-costBudget-shaping page for commercial search intent.
Comparison page
/compare/agent-search-optimization-consultant-vs-agencyDecision support for teams comparing delivery models.
Tutorial asset
/blog/how-i-optimized-this-site-for-agent-engine-searchTurns the implementation into a reusable public checklist.
Machine-readable asset
/llms.txtExplicit public context for AI crawlers and agent systems.
Crawl resource
/news-sitemap.xmlPart of the cleaner crawl and indexing layer.
Why this showcases the service
The case study shows that I do both the strategic layer and the implementation layer. This is not an audit-only service.
The report uses site-wide evidence instead of vague claims. That is a better sales asset because the proof is visible and falsifiable.
The work spans technical SEO, content architecture, AI-search readiness, internal links, schema, and conversion paths. That breadth is the offer.
The output is reusable: the same operating pattern can be applied to a SaaS site, service business, education business, content site, or founder-led consultancy.
Next moves
FAQ
No. It is the site-wide technical audit score used in this report: the share of audited URLs with no blocking issues and no warnings in the scanner. The point is not branding the score. The point is showing the actual site state clearly.
The main visible change was not one dramatic fix. It was a broader cleanup pass: stronger metadata hygiene, more support pages, clearer internal links, and a more deliberate AI-search cluster around the core service path.
No. The site was strengthened across standard SEO fundamentals too: crawl resources, page roles, metadata, schema, internal links, and conversion architecture. The AI-search angle sits on top of those foundations rather than replacing them.
Because the best showcase for this service is a site that demonstrates the work in the open. A visible before-and-after audit narrative is stronger than claiming expertise without proof.
Work with me
The audit offer is for teams that need a real picture of crawl health, structure, schema, answer surfaces, and AI-search readiness. If you want the checklist version first, the companion tutorial breaks down the exact implementation pattern used on this site.