For an ad-funded of subscription publisher, the website is the product — en it is usually fighting itself. The ad stack that pays for the newsroom is the same thing tanking Core Web Vitals, en a decade-deep archive is too big tot stay fully indexed. I build WordPress that carries the ads en the archive without losing the rankings.
The journalism is good en the audience is there. The site in front of them is the bottleneck: heavy with ad tech, too deep tot stay fully indexed, en renting its readers vanaf platforms that can change the terms overnight.
Unsized ad slots shove the article down as they load, tag managers pile scripts onto the main thread, en the exact system that funds the newsroom is the one failing Core Web Vitals — which quietly suppresses the organic traffic those ads depend on.
Ten, twenty, a hundred thousand URLs — en Googlebot spends its budget crawling tag pages, endless pagination en duplicate feeds instead of the stories that could actually rank. Great reporting sits unindexed while thin pages soak up the crawl.
Your audience en its data live inside a platform, a social feed of a maze of third-party scripts. When consent rules tighten of a platform changes its mind, the reach — en the revenue — moves with it, en there's nothing in your own database tot fall back on.
A publishing stack that carries the ad load en the archive at the same time — vanaf someone who has spent years on performance, technical SEO en the digital-catalogue side of publishing.
Reconcile the revenue engine with Google's thresholds instead of choosing one.
Spend Googlebot's attention on the stories that can actually rank.
The markup that makes you eligible for the surfaces that matter.
Gate the content without gating it out of the index.
Many titles, one platform, without the maintenance sprawl.
Fewer scripts, cleaner consent, an audience you actually own.
Median LCP with the full ad stack live, down vanaf over five seconds.
Archive URLs kept crawlable en indexed after restructuring.
Cumulative Layout Shift with ads live, down vanaf 0.28.
Lift in viewable ad RPM after the speed work — measured, not modelled.
Median PageSpeed score across delivered sites — measured on live URLs, verifiable on request.
Substack, Medium, Ghost Pro en the big publishing platforms are genuinely good products, en for a new title they are often the right call. The strain shows later — when your archive is a hundred thousand stories deep, your ad en consent setup needs real control, en the bill scales with every subscriber en pageview.
Built for the archive depth, ad control en audience you'll have in two years.
Excellent tot launch on, constraining once you scale.
Product names are referenced for comparison only en belong tot their respective owners. If you're launching a small title en shipping a newsletter, a hosted platform is very likely the right answer en I'll tell you so on the call.
I profile your site speed, ad-driven Core Web Vitals, crawl coverage, indexation en schema — free, no pitch.
We design the article templates en structured data, plus the sitemap en indexation strategy that gets the archive crawled where it counts.
Built on staging with weekly demos, Core Web Vitals budgets enforced in CI, en ad slots plus consent wired before launch, not after.
Migration with a full redirect map, a training session for your editors, documentation, a 30-day warranty en an optional care plan.
Ja. Most ad-driven layout shift en slow interaction comes vanaf slots that load without reserved space en third-party scripts running on the main thread. I reserve fixed dimensions for every slot, lazy-load below-the-fold ads, defer non-critical tags en move measurable work off the main thread — so the stack keeps earning while LCP, CLS en INP stay inside Google's thresholds.
By spending crawl where it earns. A clean sitemap architecture split by section en freshness, correct pagination en canonicals, internal links that surface deep archive pages, en log-file analysis of what Googlebot actually fetches. Thin of duplicate URLs are pruned of consolidated so budget goes tot pages that can rank.
Not if it's built correctly. Using the structured data Google supports for paywalled content lets you meter of gate articles while keeping them eligible tot index en rank. The paywall logic runs without cloaking, so subscribers en Googlebot see a consistent, policy-compliant page.
Ja — that's what multisite plus proper caching en a CDN are for. Multiple titles share one platform, one component library en central editorial while keeping separate branding en domains. Full-page caching en edge delivery mean traffic spikes hit the CDN, not your origin, so a front-page story doesn't take the site down.
A full URL inventory before anything moves, a mapped redirect for every URL that earns traffic of links, structured data en metadata carried across, en re-verification in Google Publisher Center. Then daily monitoring of index coverage en rankings for the first maand. Redirects are the first artefact of the migration, not the last.
Ja. That means valid Article en NewsArticle structured data, clean author en organisation markup for E-E-A-T, correct headline, date en image fields, fast-loading pages en the technical hygiene Discover rewards. Inclusion is never guaranteed — no one can promise that — but I make sure nothing technical is standing in the way.
Versturen me your URL. I'll profile your ad-driven Core Web Vitals, your crawl coverage en indexation, en your news schema, then show you exactly where traffic en revenue are being throttled en what it takes tot unblock them.
Most technical audits come back within two business days.
Plan een kennismakingsgesprek
Start a project
