Developer Handoff Process – Sitemap Target Keywords

Overview

As of March 2026, all sitemaps delivered to developers must include a target keyword for each page. This process change was adopted after audits of client sites (notably ^[1] and ^[2]) revealed that pages were built without any H1, H2, or H3 headings — a recurring gap that degrades SEO health scores and cannot be safely fixed after the fact through automation.

The Problem This Solves

AI-assisted SEO tooling can now automate 75–80% of on-page SEO tasks (meta titles, meta descriptions, schema injection) via the WordPress API. The one category it cannot safely automate is heading structure (H1/H2/H3), because:

Manipulating Elementor components via API reliably breaks page layouts.
Headings require contextual judgment about page content and keyword intent.
Retrofitting headings on a live site is time-consuming and error-prone.

The root cause is that developers were never told what the target keyword for a page was, so they had no basis for implementing headings correctly — or at all.

"We should make sure every developer knows that there are needs for every page. When we give them a sitemap, on that sitemap, we should say what the target keyword for each page is."
— Mark Hope, 2026-03-17 internal sync

The New Standard

When handing off a sitemap to a developer, each page entry must include:

Field	Description
Page title	The display name / nav label for the page
URL slug	The intended path
Target keyword	The primary keyword this page should rank for
Content brief (existing)	Notes on intended content, tone, or structure

With the target keyword in hand, the developer is responsible for:

Using the target keyword in the H1 (exactly once per page).
Including the target keyword (or a close variant) in at least one H2.
Adding an H3 where the page structure supports it.

Everything else — meta title, meta description, schema, alt text, internal links — can be handled post-build via AI-assisted tooling.

What AI Tooling Handles (Post-Build)

The following tasks are now automated and do not need developer attention:

Meta titles and meta descriptions (generated and injected via SEO plugin API)
Schema markup (injected via must-use WordPress plugin — see ^[3])
Image alt text (bulk-generated, with exceptions for icons/PDFs)
SEO target keyword field population in the SEO plugin

This split was validated during the Reynolds site audit, where 27 missing meta titles and 7 missing meta descriptions were fixed in minutes via AI tooling, while 23 pages with missing H1 tags required separate developer work.

Rationale

Heading structure sits at the intersection of web development and SEO. It is not traditional keyword optimization (which developers can reasonably decline), but it is also not something that can be delegated to post-build automation without risk. Framing it clearly as a developer responsibility — and providing the target keyword upfront — removes ambiguity and prevents the pattern of sites launching with no heading structure.

^[4]
^[5]
^[2]
^[1]
^[6]