Placing a schema on the site (WordPress)

The five tabs

• Create a schema: generates JSON-LD from a form, for seven types (Organization, Article, FAQPage, HowTo, Product, LocalBusiness…), flagging missing fields and adding recommendations aimed at AI citation.
• Analyze a URL: reads a live page and reports the schemas already on it.
• My library: the project's saved schemas, with title, target URL and last modification; from there you can copy the block again or delete it.
• Place on site: the real injection into WordPress, described below.
• How to inject: the manual procedures, platform by platform (WordPress, Webflow, static HTML, Shopify…), for sites PivotSEO cannot edit itself.

Connecting WordPress

• Three fields: the site address, the username and a WordPress application password (Users → Profile → Application Passwords).
• The account must be an administrator. Other roles are not allowed to insert a script into a page: the injection would go through and the script would then be stripped.
• Verify and save genuinely tests the connection to the site's REST API before saving anything; a precise message tells a credentials refusal apart from an unreachable /wp-json/.
• The password is encrypted in the database, and the connection belongs to the current project.

Placing a schema on a page

• Pick a schema from the library, paste the target page URL, click Inject.
• PivotSEO finds the WordPress post or page matching that URL, then inserts the script into its content between two markers — which is what lets it be replaced or removed later without damaging anything else.
• It then re-reads the public page to verify that the schema is genuinely there.
• Success is never announced on the strength of WordPress's own reply: only the public page counts. If the URL matches no content on the connected site, the injection is refused before anything is written.

The tracking states

• Live: the expected schema was seen on the public page.
• Other schema: the page carries JSON-LD, but not this one — often an SEO plugin imposing its own.
• Gone: no schema left on the page at all.
• Script stripped: WordPress saved the page but removed the script (see below).
• Page unreachable: the page did not answer the check.

Checking, and when the script disappears

The Check all button re-verifies every placed schema on its public page: a theme, a cache or a security plugin can remove one without warning, weeks after it was placed. When the state reads Script stripped, the account used lacks the unfiltered_html capability: try again with an administrator account, or paste the block by hand using the How to inject tab.