Network / Publishing / Package
Publisher Edition Package
For dummies · follow this order
Blue = your next action. Green = completed. You should not have to remember the workflow yourself.
1 · Prewrite BriefSEO intelligence + AIO Spy: intent, competitors, entities, PAA/PAQ, sources, internal/external links and all 5 AI systems.Create or reopen the real Tracker Prewrite here.
2 · Content RequirementsReview words, H2s, PAA/PAQ/PPS, stats, quotes and additions.
3 · Generate articleGenerate/regenerate the full article from the linked Brief.
4 · SEO PackageCheck meta, schema, links, structure and evidence.
5 · Author + imagesFinish author, styling and every image.
6 · Delivery packagePrepare the exact SEO HTML / client delivery package.
7 · Internal live URLRender the finished delivery package on a real noindex URL.
8 · Real ContentScoreScan that internal live URL with the real ContentScale scanner.
9 · ReadyOnly now is the final package verified and ready.
10 · Publish & verify livePublish the real HTML, save the exact live URL, run the pre-check and make the final manual decision.
Loading next action…
Publisher
——
Publication
——
1 · Prewrite Brief evidence
Proof of the exact research brief used at generation time. SEO Intelligence + AIO Spy.
AIO Spy · AI answer check
Uses the exact linked Prewrite keyword automatically. Same query for every AI system. Captures the real answer + exact source URLs and syncs the evidence back to the Prewrite.
No answer analysed yet.
2 · Content Requirements
Requirements detected from the linked Prewrite Brief. Review them before generating/regenerating the article.
3 · Generate article / Article preview
Protected preview — text selection, copying, context menu and dragging are disabled. This deters casual copying but cannot prevent screenshots or developer-tool extraction.
Loading…
4 · SEO Package
Meta title
Meta description
Suggested slug
Schema
Expected article URL
Built from the approved publisher domain + current slug. Step 10 uses this automatically; change it there only if the publisher publishes on another same-domain URL.
Link intelligence
One policy for the finished article: 3 verified internal URLs + 3 verified external URLs. URLs may change; only the current verified candidate set counts.
Internal URLs · 3 required
External URLs · 3 required
ContentScale discovers internal pages sitemap-first, then same-domain crawl fallback. External URLs are normalized and live-verified. If any URL changes or disappears, it stops counting until replaced and Refresh all & verify updates the article.
Manual internal fallback
Use only when automatic discovery cannot reach 3 relevant pages.
Manual external fallback
The URL is live-checked before it enters the candidate set.
Publication Standard
Required for final SEO delivery: 1200+ useful words, Direct Answer, TL;DR, linked TOC, at least 5 H2 sections and at least one mobile-friendly table.
Approved Brief Fidelity
The approved Prewrite Brief is a content contract. Planned sections, PAA/FAQ, entities, evidence links, limitations and use cases may not silently disappear during generation.
Repair reuses the immutable Approved Brief and current article, including Publication Standard checks. It does not rerun SERP, competitor, PAA or evidence research.
5 · Author & styling
Primary changes article headings. Accent changes links, quote/callout borders and other highlights. Both are scoped only to the ContentScale block.
Responsive CSS is scoped to the ContentScale block. It does not style the publisher's whole website.
Images · optional
Images never block article repair, internal live URL, ContentScore or final delivery. One active generated-image draft at a time. Choose the exact H2; subject, prompt, alt, caption and filename stay synchronized with that placement. Once uploaded, the image becomes fixed visual content and moves to Placed images below.
A. Generate a new image · H2-driven workflow v498
Featured uses the article title. Supporting uses the exact selected H2. Generated-image mode has no manual image-name field.
Choose an H2 for a section-specific supporting image. H2 numbers are shown as light guides in the protected preview.
B. Use an existing image from your computer
Choose the file first. ContentScale checks the image library by filename/name. If this image name was used before, saved alt text, caption and SEO filename are filled in automatically. You can always edit them.
Placed images
These images are already attached to the article. Use “↕ Drag image into article” and drop it on a placement line in the preview. You can also click the drag handle and then click a placement line. Click × to remove an image from this article. Its SEO metadata stays in the image library so it can be reused later.
6 · Delivery package
Final delivery is SEO-indexable HTML. JavaScript-only embeds are not accepted as final Network placements.
7 · Internal live URL
Render the exact finished delivery package on a real noindex URL before ContentScore is allowed.
8 · Real ContentScore
Scan the exact internal live URL with the canonical ContentScale scanner. A stale scan never counts as complete.
—
No ContentScore exists yet. First create the internal live URL; then run the canonical /api/scan scanner.
9 · Ready
Final state only when the real ContentScore is current for the exact current HTML.
Refresh all · verify current content
One owner-controlled check: re-read the current Brief, verify 5/5 AI, revalidate the current 3 + 3 Link Intelligence set, repair only what changed, rebuild the same internal URL and rerun ContentScore. No SERP, competitor, PAA or evidence research is rerun. If an already-live placement must change, ContentScale first reopens it explicitly for editing so live verification history is never silently overwritten.
10 · Publish & verify live
After Ready: copy the exact SEO HTML into the publisher CMS, publish a normal indexable page, enter the exact live URL, run the automated pre-check, then make the final manual decision.