Rebuilding myCast.io for search — with the dashboard to watch it move.

Content-driven discovery is the entire business model. Visitors arrive from search queries like “fan cast for [movie]” or “who should play [character]” — long-tail, high-intent, and increasingly answered by AI engines before the user ever clicks a result. A platform like that has exactly one job at the search layer: make every page legible to crawlers, citable by answer engines, and fast enough that Google’s Core Web Vitals signal isn’t actively fighting you.

When we engaged, three things were true. The site had no sitemap index covering its full URL surface. Core Web Vitals were failing on mobile — where most of the traffic lands. And the team had no shared view of what was actually broken, what was getting fixed, and what was moving as a result.

We started with the boring, foundational work — the changes that compound for years if you ship them and quietly cost you ranking surface every month you don’t. In one sprint:

Sitemap depth

sitemap.xml now returns 200 OK with 235 child sitemaps covering tens of thousands of URLs. Google can crawl the full site.

OG + Twitter cards

On every page — og:title, og:description, og:image, og:image dimensions, twitter:card=summary_large_image. Share previews work.

Heading hierarchy

H2 duplication from carousels resolved. 12 unique H2s where there used to be ~23 duplicates. Topical signals no longer diluted.

Tap targets

Raised to a 48×48px minimum. Lighthouse mobile-UX audit passes.

Meta robots

Explicit on every page — no more relying on Google defaults for a content site.

Image alt attrs

Populated sitewide. Image-search visibility unblocked.

Most agencies hand a client a 47-page PDF and call it a strategy. We’d rather hand them a live dashboard — Core Web Vitals, PageSpeed, and the weekly task board all in one place, updated every week with what shipped, what moved, and what’s next.

See the live audit dashboard→↵

The same scoreboard the myCast team sees is the same one any prospective client can review. No marketing translation layer. No quarterly review where bad numbers quietly vanish. The deliverable is the operating cadence.

The dashboard tells the whole story, but the headlines:

CLS on mobile remains the single largest finding — a hero image without explicit dimensions is reflowing the entire viewport on page load. That, plus the cast-render bundle code-split, plus shipping /sort-by-tropes/ as a real page instead of a 404, drops mobile into a defensible Core Web Vitals posture in the next sprint.

Then the AEO push: Movie / Person JSON-LD on cast pages, FAQPage schema on trope-discovery pages, and an /llms.txt manifest declaring what’s canonical for AI training and citation. Already-incidental citations from ChatGPT and Perplexity become deliberate surface. Same cadence: ship, measure, publish to the dashboard.