Tier-A Post Optimization Specs — Batch 2 (AI Automation / Consulting / SEO)

Deep-read specs for the remaining Tier-A posts (Batch 2). Like Batch 1, the copy is strong; the value is two confirmed consolidations + a systemic E-E-A-T fix + schema/linking gains.

🔴 Systemic E-E-A-T issue (fix across ALL posts — highest priority this batch)

Author attribution is inconsistent and looks fabricated: "Dr. Anjali Sharma" (operationalizing, open-source-coding), "Dr. Ananya Sharma, Head of AI Strategy" (AI-coding-costs), "Dr. Ananya Sharma, Senior Digital Strategist" (SEO-ROI). Different names + different titles for the "same" expert is a real trust liability for both readers and Google's E-E-A-T evaluation. Do: consolidate to one real, consistent author entity (single name + title + photo + bio + Person schema with sameAs to LinkedIn) used across the blog. If using personas, make them consistent and clearly real. This single fix lifts E-E-A-T across the whole site.

🔴 Confirmed consolidations

A) Merge the two AI-coding posts. ai-coding-agent-costs-free-alternatives and open-source-ai-coding-disruption are near-duplicates — same intent (Claude Code $20–200/mo vs free Goose), same comparison table, same pitch. Action: consolidate into ONE canonical post (suggested title: "AI Coding Agent Costs: Free & Open-Source Alternatives (2026)"), keep the richer FAQ set (open-source post has 6), and 301 the other into it. Also check a referenced third post (ai-agent-developer-economics) for the same overlap — likely fold in too. B) Redirect the dated 2025 AI-search post. Confirmed by reading digital-marketing-in-2026: it supersedes google-ai-search-digital-marketing-2025 (broader, current, same intent). 301 the 2025 post → digital-marketing-in-2026 (resolves the Batch-1 hold item).

Per-post specs

1. operationalizing-ai-for-scale-and-sovereignty — AI automation/consulting (strong)

• State: ~2,500w, answer-first, FAQ ×4, service + consultation CTAs, cites MIT/Reuters/Economist + GDPR/DPDP. Title "…The 2026 Imperative."
• Do: confirm/add FAQPage + Article + Person schema; add explicit link to /services/ai-automation/ + /services/ai-consulting/ (once live) high in body; keep "Turn This Intelligence Into Business Growth" CTA. Strong enterprise/"AI-first business" intent — good for the consulting cluster.
• Indexing: P1. Cannibalization: none.

2. ai-native-cloud-infrastructure-disruption-developer-empowerment — strategic (strong)

• State: answer-first ("$100M Bet Against AWS"), comparison table, FAQ ×4, service links, cites MIT/Economist/Reuters.
• Do: confirm/add schema; tighten the commercial tie — add one line + link "we help enterprises navigate this → AI consulting"; ensure it links to the GEO/automation cluster, not just the lab.
• Note: slightly more trend-commentary than commercial; fine as a Tier-A authority/thought-leadership spoke. Indexing: P2.

3 + 4. ai-coding-agent-costs-free-alternatives + open-source-ai-coding-disruption → MERGE (see above)

• Canonical (keep one): answer-first, comparison table, 6 FAQs, "How A Square Solutions Can Help," Claude-Code-operator-track link. Do on the survivor: add FAQPage/Article schema; add /services/ai-automation/ + /services/ai-consulting/ links; fix author; remove the off-topic JWST/biosignature internal link (thematic drift noted in the read). 301 the loser.
• Indexing: P2 (after merge). Cannibalization: the reason for the merge.

5. build-business-website-with-ai — (not re-read this batch; spec carried)

• Do: confirm it's commercial/how-to (not thin); answer-first intro; FAQ + schema; link to /digital-marketing-uk/ + /services/ai-automation/; CTA to consultation. Indexing: P2. (Flag: skim to confirm depth; demote to Tier-B if thin.)

6. calculating-seo-roi-google-analytics — SEO commercial (strong)

• State: answer-first, ROI framework + attribution + stats (53% organic, 7x ROI), FAQ ×4, links "AI-native marketing services for UK businesses", "Request SEO ROI + GEO Audit" CTA, dated 16 May 2026.
• Do: confirm/add schema; add link to /services/technical-seo/ (ROI measurement ↔ technical SEO) once live; this is a strong Technical-SEO cluster spoke + conversion asset.
• Indexing: P1. Cannibalization: none.

7. digital-marketing-in-2026 — Digital Marketing UK pillar-spoke (strong)

• State: comprehensive, answer-first (3 permanent shifts), GEO section, 2026 stack, India context, FAQ ×4, links GEO + /digital-marketing-uk/, cites Google/Moz, references ScamCheck/TrustSeal.
• Do: confirm/add schema; make this the canonical recipient of the 2025-post redirect; ensure a strong link to /digital-marketing-uk/ (money page) above the fold; add author/Person schema.
• Indexing: P1.

Cross-cutting (all Batch-2 posts)

• Confirm FAQPage + Article + Person schema is actually emitted (systemic "schema not visible" across reads — likely the biggest snippet/E-E-A-T lever).
• Link to the 3 new service pillars (ai-automation, ai-consulting, technical-seo) once published — these posts currently link to generic /services/ or the lab, not the specific money pages.
• Single consistent author entity (the E-E-A-T fix above).
• Remove off-topic internal links (e.g., JWST/biosignature) that cause thematic drift.

Manual-indexing priority (Batch 2)

P1: operationalizing-ai, calculating-seo-roi, digital-marketing-in-2026. P2: ai-native-cloud, the merged AI-coding post, build-business-website-with-ai (after depth check). Redirect (no indexing): the 2025 AI-search post → digital-marketing-2026; the duplicate AI-coding post → canonical.

Combined Tier-A status (Batch 1 + 2)

• Strong, keep+improve+index: GEO guide, ChatGPT Search, AI-Overviews "Real Data 2026", ScamCheck, operationalizing-ai, calculating-seo-roi, digital-marketing-2026.
• Keep, narrow scope: AI-Overviews "38% study", ai-native-cloud.
• Fix gaps then index: TrustSeal (add FAQ+schema), ScamCheck (add consulting link).
• Consolidate/redirect: 2025 AI-search → digital-marketing-2026; the two AI-coding posts → one.
• Sitewide: consistent author entity + confirm schema emission + link to new service pillars.