Give Publisher reliable URLs and evidence, then let it create contextual links and hand metadata to the active WordPress SEO plugin.
SEO & Links fields
| Field | Default/values | Behaviour |
|---|---|---|
| Internal links | Default 4 | Requested count of relevant allowed internal destinations |
| External links/sources | Default 2 | Requested number of verified relevant external sources |
| Sitemap | Automatic or manual URL | Manual override wins; otherwise Publisher detects common sitemap locations |
| SERP provider | None or Serper; default None | Adds optional result evidence to research |
| SERP country | Default ee |
Localises optional Serper research |
| SERP results | Default 10 | Requested result depth for optional research |
Sitemap discovery
Publisher checks supported SEO-plugin conventions and common endpoints including /sitemap_index.xml, /sitemaps.xml, /wp-sitemap.xml and /sitemap.xml. Detection is cached for about 12 hours and child sitemaps can be scanned. Enter a full manual sitemap URL only when automatic detection chooses the wrong source or a custom setup requires it.
Internal links
Publisher builds an allow list from real inventory URLs, chooses contextually relevant same-language destinations and uses each destination once. The desired count is a target. If the site has fewer genuinely relevant pages, the job records the actual count and a warning instead of inserting unrelated links.
External citations
External sources must be relevant and verifiable. Optional Serper evidence can help discover sources, but Serper is not required. A source shortfall is non-blocking when no suitable evidence exists; exceeding safety caps or using invalid/unapproved destinations can block quality.
SEO-plugin hand-off
Publisher writes supported title, description, focus keyword, canonical and social metadata. Provider precedence is SEOPress, then Yoast, Rank Math and AIOSEO when multiple integrations are detected. The SEO plugin remains responsible for its own frontend output and schema implementation; Publisher does not expose a separate schema builder.
After publication
Publisher refreshes the canonical URL, checks sitemap presence, can submit IndexNow automatically and records a Search Console snapshot when connected. These signals confirm hand-off, not guaranteed indexing or ranking.
Recommended setup
- Test automatic sitemap detection.
- Open the detected URL and confirm that current site content is represented.
- Use a manual override only if necessary.
- Start with 4 internal and 2 external links.
- Generate a Draft and verify every destination in context.
- Check the active SEO plugin’s fields and frontend source.
- Connect Serper or Search Console only when the base workflow is stable.
Troubleshooting
- Sitemap not found: verify public access and enter the correct full index URL.
- Too few internal links: inspect inventory and language; accept a documented shortage if no relevant destination exists.
- Wrong target: correct the source inventory/taxonomy and regenerate; do not force a URL solely to meet the count.
- No SEO fields: verify the supported SEO plugin is active and only one provider should be authoritative.
- Not indexed: check canonical, robots, sitemap and Search Console separately; publication does not guarantee indexing.
Verification checklist
- Detected/manual sitemap opens and is current.
- All internal destinations exist, are relevant and match the language.
- Citations support nearby claims.
- Report shows requested and actual counts honestly.
- Canonical and SEO metadata appear through the intended plugin.
Related guides
Inventory and cannibalisation · GSC and Serper · Quality reports