The Dev Handoff That Makes SEO Actually Work

Every SEO strategy document we've ever inherited was 'correct' — and 60% unimplemented or implemented wrong. SEO is an engineering deliverable. Schemas, canonicals, crawl paths and templates either ship in code or they don't exist.

The build-vs-plugin line

Every plugin is a dependency with its own author, roadmap and security record. Our line: if a requirement is core to the business and stable, build it natively; if it's peripheral and moving, rent it.

Custom code is not automatically better — badly written custom code is worse than a mature plugin. The calculus is control over the parts that make you money versus maintenance on the parts that don't.

A healthy WordPress or Shopify build in 2026 is quietly boring: few dependencies, all understood, everything load-bearing owned.

Signs your rebuild is overdue

1. Every change request returns with a bigger estimate than the last one
2. Two plugins conflict and the fix is a third plugin
3. Mobile LCP is over 4 seconds and nobody remembers why
4. The last person who understood the theme left a year ago
5. Marketing has a private doc of 'things the website can't do'

Integration is where builds actually live

Nobody's website is an island — it syncs stock, posts leads to a CRM, fires events to analytics, and triggers email. These seams are where projects overrun and where launches leak data.

We map every integration with its failure mode: what happens when the CRM is down, when the rate limit hits, when the API token expires on a Saturday. Every mapping gets a queue, a retry, or a human alert.

A website is a frontend for your operations. Builds that respect that ship on time; builds that discover it at go-live get a second, more expensive timeline.

The best code on a client site is the code nobody has to think about for five years.ALIFY engineering notes

Performance is architecture, not decoration

Speed work fails when it's scheduled as polish at the end — by then the decisions that mattered are entrenched: a builder emitting four wrappers per element, a slider library loaded for one page, fonts subset for nobody.

We budget performance like features: a 100-point Lighthouse target has an implementation plan from the wireframe. Image pipelines, script governance and font discipline are agreed before visual design polishes anything.

Audit before architecture

Every rebuild that goes smoothly started with an inventory nobody wanted to write: templates in use, plugins with business logic buried inside, integrations with tribal knowledge as documentation. Skipping the audit doesn't save the week — it bills the month.

We export the plugin list, crawl every template, and interview whoever touches the site weekly. The output is a one-page map of what the site actually does, as opposed to what anyone remembers it doing.

Ninety percent of rebuild surprises were knowable on day three. The other ten percent are why timelines have buffers, not excuses.

We don't do rescue projects anymore. We do builds that never need rescuing.Humdan Ali, founder

Where to start this week

Take your SEO's last audit and mark every item 'content', 'template' or 'server'. Anything not explicitly assigned to a developer is a wish, not a requirement.

Then keep it honest with a short list:

• Backups verified by an actual restore, not a green dashboard icon
• Rollback plan rehearsed: one command back to last-known-good
• Error monitoring on production with an owner assigned
• Put the date on the calendar — playbooks without Fridays are just reading

And when the scope outgrows the spreadsheet, that's precisely what our team is for.

Straight answers

Can you maintain a site another agency built?

Yes — it starts with a two-week stabilisation pass: backups, update hygiene, security baseline and a written map of what we found. After that it's a standard care plan with full transparency on findings.

What does post-launch support look like?

A named engineer, a queue with response times, monthly reports on updates, uptime and performance — and quarterly advice on what we'd fix next. No ticket black holes.

Do you work with our existing theme or start over?

Both. We audit first: if the theme's bones and editor experience are sound, we harden and extend. Most inherited builders fail that audit on performance grounds, which is when a lean custom theme becomes the cheaper option over three years.