Ongoing · Design, build & SEO

yasser-shkeir.com

This site, run like a client engagement. On 2026-07-19 I audited it exactly the way I'd audit a prospect's site — crawlability, indexing, performance, accessibility — published what I found, and started fixing it in public. The numbers below are the real before values.

Visit live

The audit

The audit found real problems, the kind I get hired to find on other people's sites.

The worst one: every non-home page declared the homepage as its canonical URL. To a search engine, that's a sitewide instruction to deindex everything except the homepage.

  • Every non-home page declared the homepage as its canonical — a sitewide deindex instruction
  • robots.txt blocked /_next/, so Googlebot couldn't fetch the site's CSS or JS — and blocked the OG image route
  • Apex and www both served 200, splitting link equity — a client's dofollow backlink pointed at the apex
  • First-load JS measured ~244 KB brotli against a 130 KB budget
  • One text color token measured 3.28:1 contrast — below WCAG AA — across ~71 usages

The fixes

Canonicals came first, because they were quietly deindexing the site. Measured 1 page with a correct canonical; re-measured after the fix: 8. Every page now declares itself.

The robots.txt blockers were removed: Googlebot can fetch CSS and JS, and the OG image route is crawlable. The apex/www split, the JS budget overrun, and the contrast failure each get the same treatment — fix, then re-measure — and their after values are published here once measured, not before.

Before and after, in public

The before values, the fixes, and the methodology all live on this page. Each number says how it was measured, so any prospect can re-run the checks and get the same answers.

That's the point of this case study: it's the same audit I'd run on your site, run on mine first.

Stack

Next.jsTypeScriptTailwind v4Vercel

Other work