Add the Markup You Need Without Letting Custom HTML Override Core SEO Policy
Aegisify SEO 2.9.4 Custom Injections supports Google/Bing verification values, validated site-wide JSON-LD, advanced head markup, and footer markup while stripping several SEO directives that Aegisify intentionally owns through dedicated settings.
VerifyJSON-LDHeadFooter
Know Which Values Are Independent and Which Require the Injection Switch
Search verification is intentionally separate from optional HTML injection; custom schema/head/footer use the injection master control.
Click a stage to expand
01VerifyGoogle / Bing
02ValidateJSON only
03Sanitizehead/footer
04ProtectSEO-owned tags
05Renderpublic only
06Testfront end
Keep Search-Engine Ownership Verification Simple and Independent
Google and Bing verification are configured in this area but are rendered independently of the optional custom-injection master switch.
google-site-verification
The Google value is treated as the meta content value and emitted as a dedicated google-site-verification tag. This avoids requiring an administrator to paste an entire arbitrary head snippet for a basic ownership token.
msvalidate.01
Bing input accepts either the bare verification token or the complete Bing meta tag. Aegisify extracts the content value, removes unsupported characters, bounds the token length, and reports an invalid input when nothing usable remains.
Bing Token Changes Reset IndexNow Health State
When the saved Bing verification value changes, Aegisify clears the previous IndexNow health result so the Search Console workflow does not continue displaying stale ownership-health evidence.
Verification Does Not Need Custom HTML Enabled
The front-end output prints configured Google/Bing verification before checking the custom-injection master switch. That keeps simple ownership metadata independent from advanced snippets.
Add Extra Structured Data Only When the JSON Is Valid
Custom schema is for additional structured data that the normal Meta & Schema controls do not already own.
Decode Before Save
A non-empty custom schema value must decode as JSON into a valid structured object/array. Invalid JSON produces an admin settings error and is not accepted as the new saved schema value.
Re-Encode the Parsed Structure
Valid input is stored through WordPress JSON encoding rather than preserving arbitrary whitespace or non-JSON wrappers. At output, it is decoded again and emitted inside an application/ld+json script.
Valid JSON Is Not Automatically Valid Schema
Aegisify verifies JSON syntax, not whether every property is appropriate for Schema.org or a search-engine feature. Administrators still need to avoid duplicating entities already emitted by Aegisify’s normal schema graph.
Allow Advanced Markup, but Protect Aegisify-Owned SEO Tags
The head area supports bounded advanced markup while actively removing several classes of conflicting SEO output.
On save, Aegisify removes NUL bytes and PHP open/close tags. If the snippet contains a meta description, the tag is removed and a warning directs the administrator to Titles & Meta or the per-content SEO fields. If a robots meta contains noindex or nofollow, Aegisify removes it and directs the administrator to the content-level indexing controls.
At output time, the head snippet is filtered again. Negative robots metadata is stripped, meta-description tags are removed again, and custom canonical <link rel="canonical"> output is stripped so Aegisify’s canonical system remains the single owner. The remaining markup is passed through a head-specific allowlist that supports selected meta, link, script, style, and noscript elements/attributes.
Support Integration Markup With a Broader Footer Allowlist
Footer markup goes through the same master switch and SEO-policy stripping, but the allowed HTML surface is broader because visible/integration elements may legitimately belong near the page end.
The current footer allowlist starts with supported head elements and adds bounded attributes for div, span, p, a, img, iframe, br, em, and strong. Common link/image/iframe attributes such as source URLs, dimensions, loading, rel, referrer policy, classes, IDs, and selected data attributes are explicitly enumerated.
That makes the feature useful for approved third-party widgets, measurement snippets, embed containers, or other integration needs, but it should not be treated as an unrestricted application deployment mechanism. Third-party scripts can affect privacy, Core Web Vitals, browser security policy, consent requirements, or availability even when their markup passes Aegisify’s structural filtering.
2.9.4 Applies Multiple Layers Before Custom Markup Reaches the Page
These controls reduce accidental SEO conflicts; they do not replace code review for third-party snippets.
unfiltered_html receive WordPress post-HTML sanitization before storage.wp_kses allowlists even after stored values pass save-time handling.Use the Feature for Missing Integration Surface—not to Rebuild Existing SEO Controls
The safest custom injection is the one that has a clear owner and cannot be configured cleanly elsewhere.
Use dedicated Aegisify controls for titles, meta descriptions, canonicals, robots directives, social metadata, normal schema mappings, sitemaps, Search Console, and IndexNow. Use Custom Injections only for an approved verification/integration/schema need that those surfaces do not already cover.
Add What You Need Without Duplicating Core SEO Signals
Use Aegisify SEO Custom Injections when a verified integration requires extra markup, while keeping descriptions, canonicals, and indexing policy under their dedicated controls.
Common Questions About Advanced Head and Footer Output
Do I need to enable Custom Injections for Google or Bing verification?
The current front-end output renders configured Google/Bing verification values independently of the injection master switch.
Can I paste another meta description into Head Injection?
Aegisify removes meta-description tags from the custom head snippet because the plugin owns the single managed page description through dedicated metadata controls.
Can I set noindex or nofollow through Custom Injections?
Aegisify strips negative robots meta from custom injection and directs those decisions to the per-content indexing controls.
Can I inject a second canonical URL?
Custom canonical links are stripped from rendered head injection so the Aegisify canonical system remains the managed source.
Does valid custom JSON-LD guarantee a rich result?
No. The setting validates JSON syntax. Structured-data correctness, search-engine eligibility, page content, and search-engine decisions remain separate.
How can Aegisify AI help?
Ask about Aegisify or WordPress: errors, plugins, security, SEO, compatibility, troubleshooting, comparisons, or launch a free website scan.