Add optional search evidence and multilingual context without making the core Publisher pipeline dependent on either service.

What is optional

Google Search Console and Serper enrich topic and research decisions. Neither is required to create an article. Without them, Publisher continues with the WordPress inventory, topic configuration and model context and records the unavailable optional evidence.

Search Console fields

The Integrations & Advanced screen accepts a Google OAuth web-client configuration, redirect details and an exact Search Console property value. Publisher 3.7.6 does not provide a property picker; copy the property exactly as it appears in Search Console, including URL-prefix or domain-property syntax.

Search Console setup

1. Create or select a Google Cloud project.
2. Enable the required Search Console API.
3. Create an OAuth web application.
4. Add Publisher’s displayed authorised redirect URI exactly.
5. Save the client ID and client secret.
6. Start OAuth and grant the minimum requested account access.
7. Enter the exact property that the authorised Google account can access.
8. Test and confirm that Publisher reports a usable connection.

Search Console evidence can support query/page opportunities and daily publication snapshots. It does not guarantee indexing, position or traffic.

Serper fields

There is no separate Serper usage-limit field in 3.7.6. Usage and billing limits are managed in the Serper account. The connection test itself can consume provider quota.

Graceful fallback

• No GSC connection: topic inference and article generation continue without Search Console opportunity data.
• No Serper key/provider: research continues without external SERP results.
• Too few verified sources: Publisher records a non-blocking shortfall instead of fabricating citations.
• Temporary integration failure: inspect the report and logs; do not assume the article itself is invalid.

WPML and Polylang

Publisher uses the chosen strategy/topic language, filters inventory and links accordingly and assigns the generated post and taxonomy terms through WPML or Polylang when active. It does not translate an existing article into every language automatically unless separate language-specific topics/jobs are created.

Without a multilingual plugin

The Content language compatibility setting defaults to Site/detected and Publisher resolves the WordPress locale. There is no normal global language field on Content settings; language is primarily chosen with topic strategy and individual topic context.

Recommended rollout

1. Prove a complete Draft without GSC and Serper.
2. Connect Serper, run one narrow topic and compare research/report evidence.
3. Connect GSC with the exact property and confirm a usable data response.
4. For multilingual sites, test one Draft per language and verify taxonomy, author and internal links.
5. Keep integrations optional in operational expectations.

Troubleshooting

• Redirect mismatch: copy the displayed redirect URI exactly into Google Cloud.
• Property denied: verify the authorised account and exact property syntax.
• No GSC data: the property may be new, have no impressions or not contain the expected date/query evidence.
• Serper authentication/quota: verify key and account usage; there is no Publisher-side quota control.
• Wrong language links: repair source post language assignments and rebuild inventory.

Verification checklist

• Core generation works with both integrations disabled.
• OAuth redirect and exact property are documented securely.
• Serper country matches the target market.
• Reports clearly state which optional evidence was available.
• Each multilingual Draft has correct language and same-language links.

Related guides

Topic strategy · SEO and sources · WordPress language assignment