seo

Switching the rating flag off is not enough while card badges and aggregateRating markup still ship. My notes on sweeping every surface clean.

TL;DR: Switching off ratings hid the detail page section but cards and JSON-LD still showed the old score from cached property data. That mismatch between what users see and what crawlers read risks spam penalties. Now the rating_enabled flag gates both the UI badge and the structured data so everything disappears together.

242 client names used to live inside one image. Now they are indexed text, readable by screen readers, with a total computed from the data.

TL;DR: Client names were locked in a JPEG, invisible to screen readers and Google. The fix moved 242 names into a typed TypeScript module grouped by sector and rendered them as real searchable HTML with Next.js. The image stays for visual proof under WCAG's logo exception, while live text keeps the list accessible, indexed, and always in sync.

Replacing [PLACEHOLDER] with verifiable facts, and why generic filler sits close to Google's scaled content spam signal.

TL;DR: Generic filler text on placeholder company cards isn't a fix; Google flags scaled content abuse, and hollow copy signals spam. Real research produced verifiable facts like sectors, cities, and founding years, applied consistently across both locale files. Type validation only checks strings, not quality, so content deserves first-class treatment.

Canonical, hreflang, metadataBase, and JSON-LD LocalBusiness: the three layers that made sixteen bilingual Next.js routes pass an SEO audit.

TL;DR: Sixteen bilingual Next.js routes passed a full SEO audit thanks to one metadata commit. Three layers did the work: a shared helper generating canonical and hreflang tags, metadataBase in the root layout, and JSON-LD marking up the business and website. Centralizing everything keeps URLs consistent, so new routes stay audit-proof instead of relying on Google to guess.

An audit of a news site with 9,200 articles in its sitemap and almost nothing indexed: crawl demand, internal linking, and the fixes that actually matter.

TL;DR: An audit of a news site with 9,200 articles in its sitemap found only about 44 that ever earned a Google impression, dropping to zero for the most recent publish months. Every technical check came back clean, so the problem is crawl demand: publishing volume far outpacing authority signals, plus an archive cut off from internal links. The fixes are editorial: lower the volume, build contextual links into old content, trim the news sitemap, and earn external validation.

A red "Couldn't fetch" status in GSC does not mean your sitemap is 404. Here is the server-side diagnosis order.

TL;DR: Google Search Console showed a sitemap "Couldn't fetch" error, but server checks proved all 147 URLs returned HTTP 200 and Cloudflare blocked nothing. Per Google's docs, the message only means the last fetch attempt failed, often due to timeouts or a crowded crawl queue. The fix is patience: don't resubmit, wait a few days, then recheck.

A per-need comparison of ChatGPT, Claude, Gemini, and Perplexity, plus where consumer assistants meet self-hosted agent runtimes: OpenClaw, Hermes Agent, and Agent Zero.

TL;DR: The best AI assistant in 2026 is no longer about the smartest chatbot but about persistence and autonomy. Pair a strong brain like ChatGPT or Claude with a self-hosted agent runtime such as OpenClaw, Hermes Agent, or Agent Zero for memory and autonomous execution. Go hybrid: match tools to your workflow instead of chasing one all-in-one winner.

Snippet changes used to mean an edit, a commit, and a deploy wait. A whitelisted settings endpoint turns that into one PUT request.

Adding fallback icons for categories without one made the sidebar jump. Explicit width/height on images, and og:image dimensions, keep CLS under control.