Skip to content
SyndiScribe AI

Support

Resources for a calm SyndiScribe AI rollout.

Key answers for launching the plugin locally, in two languages and with a beginner-friendly setup.

  • Checklists
  • Common issues
  • PL/EN support
SyndiScribe AI support with checklist, status and rollout guidance

Do I need to code?

No. The first run can be done in WordPress: add a source, choose drafts and review the result.

Is AI required?

No. SyndiScribe AI can run as a regular importer. AI can be enabled later with usage limits.

Is the site bilingual?

Yes. Polish and English pages are ready with a language switcher.

Is Yoast required?

No, but SEO descriptions are prepared so Yoast can use them when active.

What is prepared?

The local WordPress site includes Polish and English pages, SEO descriptions, generated visual assets, a beginner guide, dedicated SEO, automation and use-case pages, plus Polish plugin messages in the WordPress admin.

Core pages

The homepage explains the plugin. The features page covers import, AI, media, queues and duplicates. The beginner guide helps people who are not comfortable inside WordPress.

Topic pages

Dedicated sections explain WordPress SEO, publishing automation and practical use cases such as blogs, portals, WooCommerce, YouTube, agencies and knowledge bases.

Checklist before the first import.

This list helps start safely without accidentally publishing unfinished content.

1. Choose one source

Do not add ten feeds at once. Start with one source and see how the import behaves.

2. Use drafts

Draft status keeps content invisible to visitors until you approve it.

3. Limit item count

Use 1-3 articles per run while checking titles, images, categories and SEO descriptions.

4. Read logs

Logs explain what worked, what was skipped and what needs attention.

Common issues and first checks.

Most problems can be narrowed down without code when you check the right place.

Symptom Possible meaning What to do
No new post appeared The source has no new items, the item was a duplicate or the job is still queued. Check queue, logs and duplicate settings.
Image is missing The source did not provide an image or the file was too large, invalid or unreachable. Change the main image mode or review file size limits.
AI is not working An API key is missing, a limit was reached or the selected provider is unavailable. Check the AI account, usage limits and log message.
Content is too long The source provides full articles or the template does not shorten text. Use excerpt settings, transform rules or a shortening prompt.