Article Writing Services for Knowledge Bases: Scale Software-led Drafting with Editorial Checks and a Structured Blog Writer

Knowledge bases and help centres often begin as a small collection of useful answers. Then the product grows, support questions multiply, and marketing teams start publishing articles around every variation of a customer problem. Before long, the site has several pages targeting almost the same query, with overlapping headings, competing internal links and no clear primary URL.

That is where keyword cannibalization becomes expensive.

An article writing service for knowledge bases needs to do more than produce grammatically correct drafts. It must understand search intent, separate product documentation from educational content, identify SEO keyword overlap and support a structured editorial review before anything reaches the live site.

SEOLetters is built for this workflow. It helps you move from keyword research and topic planning to structured article drafting, internal linking, schema, images and publishing. You can use it to build a knowledge base that expands without creating a collection of serp ranking conflicts.

If you are looking for a software-led blog writer that can support a repeatable SEO publishing operation, explore SEOLetters for article drafting and publishing.

Why Knowledge Base Content Creates Keyword Cannibalization Risk

A knowledge base usually has a different purpose from a conventional company blog. Its pages may explain features, resolve technical issues, define product terminology, answer pre-sales questions or guide users through a process.

Those subjects are useful, but they can sit very close together in search:

• “How to create a project dashboard”
• “Project dashboard best practices”
• “What is a project dashboard?”
• “Project dashboard templates”
• “Project dashboard reporting”
• “Why is my project dashboard not updating?”

A search engine may struggle to understand which page should rank for a broad phrase such as project dashboard. Your pages then compete with one another, split backlinks and collect partial relevance signals. This is the basic shape of a keyword cannibalization problem.

The difficulty increases when a business uses an article writing service that treats every keyword as a new article opportunity. That approach can generate volume quickly, but it does not always create a coherent information architecture. Basically, the content calendar becomes busy while organic performance stays uneven.

The difference between useful coverage and SEO keyword overlap

Topical coverage is valuable when each page has a distinct purpose. Overlap becomes a problem when multiple URLs answer the same question for the same audience at the same stage of the buying or learning journey.

Content situation	Likely outcome	Recommended action
Two pages answer the same question with similar wording	Keyword cannibalization	Consolidate or redirect
One guide targets a broad topic and several pages address specific tasks	Healthy topical depth	Keep, then improve internal links
A help article and blog post target the same intent	Search intent confusion	Reposition one page or merge them
Several old pages have weak traffic and overlapping headings	Diluted authority	Run a keyword cannibalization audit
Product documentation ranks for an educational query	Misaligned page type	Create or optimise a suitable guide
Pages target similar terms but serve different users	Potentially acceptable	Clarify titles, schema and internal links

The answer is not to avoid publishing. It is to make each article carry a defined role.

What an Article Writing Service for a Knowledge Base Should Actually Do

A conventional writing service may focus on briefs, drafts and revisions. For an SEO knowledge base, the workflow needs to be broader because the article is one part of a connected system.

A capable service or software platform should help you with:

• Keyword discovery and difficulty assessment
• Search intent mapping
• Topic clustering and topical authority planning
• Existing-page analysis
• Keyword cannibalization detection
• Article outlines with structured headings
• Product-aware and audience-aware drafting
• Internal link recommendations
• FAQ and schema opportunities
• Editorial checks
• Image and media prompts
• Direct publishing to your CMS
• Performance monitoring and content refreshes

This is where software can offer a practical advantage over a purely manual process. A human editor may understand your product deeply, but manually checking hundreds of URLs, keyword records and internal links takes time. A structured platform can handle the repetitive parts and leave your team to review claims, examples and brand standards.

The role of SEOLetters in the workflow

SEOLetters acts as an AI writing engine and publishing workflow for teams that need more than isolated blog posts. You can bring your own AI keys and route different stages to Gemini, OpenAI or Claude, depending on your preferences and operating model.

The platform supports:

• Keyword research with difficulty ratings
• Topical authority clusters
• Competitor site-gap analysis
• Structured article generation
• Internal linking
• Schema and image support
• Product-aware content
• Multi-language generation across 21 languages
• Publishing to WordPress, Shopify or webhooks
• Autonomous campaigns with a chosen topic, cadence and destination
• Content-refresh campaigns for existing pages
• Performance tracking after publication

That whole thing matters because knowledge base growth is rarely a one-off exercise. You need a repeatable process that can produce useful drafts, flag potential conflicts and keep older articles current.

Keyword Cannibalization in Help Centres: The Main Causes

Keyword cannibalization does not always come from deliberate bad planning. It often appears gradually as different teams publish for different reasons.

1. Separate teams target the same customer question

Product marketing may publish “Best ways to use workflow automation”, while customer support publishes “How to automate a workflow”. Both pages may use the same target phrase, similar headings and comparable examples.

The intent could be different, but the distinction may not be clear enough for users or search engines. If both URLs attract the same impressions, this is a sign that you need a more deliberate search intent mapping process.

2. Product documentation and blog content overlap

A help centre article may explain how a feature works. A blog article may discuss the feature’s benefits. Both might target “how to use customer segmentation”, even though one belongs in product support and the other belongs in an educational content hub.

A page type is not enough to create differentiation. The copy, title, headings, structured data and internal links need to reinforce the difference.

3. Variations of one keyword become separate articles

Writers sometimes treat close variants as separate opportunities:

• Knowledge base software
• Knowledgebase software
• Knowledge base tool
• Help centre software
• Customer support knowledge base

These phrases may represent a single commercial topic. They could also represent distinct intents, but that should be tested against the SERP, not assumed from a keyword list.

4. Content refreshes create duplicate URLs

A team publishes a new, improved version of an article rather than updating the existing page. The old page remains indexed, perhaps with backlinks and historical rankings.

This can create a form of duplicate content SEO issue. The pages may not be exact copies, yet they offer similar information and compete for similar queries. A canonical tag can help in some situations, but consolidation, redirection or a clear content hierarchy may be more appropriate.

5. Automated production ignores the existing site

High-volume AI writing can make this worse if the system does not assess your current content. Every new article should be checked against existing URLs, primary keywords, entities, headings and search intent.

SEOLetters supports the planning side of this process so you can build content from a site-wide view rather than treating every brief as an empty page.

How to Map Search Intent Before Drafting

Search intent mapping is the foundation of safe knowledge base expansion. It asks a practical question:

What does the searcher need to accomplish, and which page type should satisfy that need?

A useful classification system includes:

Intent category	Searcher need	Suitable knowledge base content
Informational	Understand a concept	Glossary page, beginner guide, explainer
Procedural	Complete a task	Step-by-step help article
Troubleshooting	Resolve an error or failure	Diagnostic article, error guide
Commercial investigation	Compare approaches or tools	Comparison guide, use-case article
Transactional	Start, buy or configure	Product page, setup page, pricing content
Navigational	Find a known feature or resource	Feature page, support hub, documentation index

Consider the phrase email automation workflow. It may represent several different needs:

• A beginner wants to understand what the term means.
• A user wants instructions for creating one.
• A manager wants examples for a marketing team.
• A buyer wants to compare email automation tools.
• An existing customer needs to fix a failed trigger.

These should not automatically become five pages. First, identify whether the SERP supports separate page types and whether your audience benefits from distinct answers.

A practical search intent mapping framework

Use this five-step process before generating an outline:

1. Record the primary keyword and close variants. Include synonyms, questions, long-tail terms and product language.
2. Review the current SERP. Note the dominant page types, common subtopics, featured snippets and recurring questions.
3. Assign an intent category. Choose the main user need, then record secondary intent where relevant.
4. Compare existing URLs. Identify pages that already satisfy the same need.
5. Define the page’s unique job. State what this article will answer that another URL should not.

The final step is often skipped. Do not skip it.

A useful editorial brief might state: “This article explains how small SaaS teams can design an internal knowledge base. It does not provide product-specific setup instructions, which belong in the help centre.”

That one sentence can prevent a great deal of overlap.

Building a Keyword Cannibalization Audit into the Editorial Process

A keyword cannibalization audit should not be an annual emergency. It can be built into every content campaign, especially when publishing at scale.

What to check during an audit

Review the following signals:

• Multiple URLs ranking for the same primary phrase
• Similar title tags and H1 headings
• Shared secondary keywords
• Overlapping search intent
• Pages with impressions but weak click-through rates
• Pages that alternate rankings for the same query
• Internal links pointing to different URLs for the same topic
• Old articles competing with newer, more complete pages
• Blog content ranking for product-support queries
• Help centre content ranking for broad educational queries

A single ranking position does not prove cannibalization. Search engines sometimes show several pages from one domain because they are genuinely relevant. The pattern becomes more concerning when rankings fluctuate, traffic is split and neither URL has a clear purpose.

A simple scoring rubric

You can score each page pair from 0 to 3 across five criteria:

Criterion	0 points	1 point	2 points	3 points
Keyword similarity	Very low	Some overlap	Strong overlap	Almost identical
Search intent	Different	Partly related	Mostly similar	Identical
Audience	Different	Some shared users	Similar audience	Same audience
SERP footprint	Separate results	Occasional overlap	Frequent overlap	Same queries
Content coverage	Different subject	Some shared sections	Similar article	Near duplicate

Interpret the total as follows:

• 0 to 4: Low risk. Keep separate, but maintain clear links.
• 5 to 8: Moderate risk. Clarify titles, intent and internal linking.
• 9 to 12: High risk. Consider consolidation or a stronger content hierarchy.
• 13 to 15: Severe risk. Merge, redirect or fully reposition one page.

This is not a replacement for judgement. It is a way to make editorial decisions more consistent across a large site.

The Editorial Checks That Keep Software-Led Drafting Safe

AI software can create a structured first draft quickly. It should not be treated as an unreviewed subject matter expert, particularly for technical documentation, regulated industries or product instructions.

Your editorial checks should cover four layers.

1. Factual and product accuracy

Check:

• Feature names
• Interface labels
• Product limits
• Integration requirements
• Pricing or plan references
• Technical commands
• Compliance statements
• Screenshots and workflow steps

If an article explains a software feature, test the process in the current product version. A polished article with an incorrect button name will create support tickets rather than reduce them.

2. Search and information architecture

Check:

• One clear primary intent
• A distinct target URL
• Logical H2 and H3 headings
• Descriptive title and meta description
• Appropriate internal links
• No unnecessary repetition of the main keyword
• Canonical and redirect requirements
• Related articles that should be merged or updated

The article should make sense as part of the knowledge base, not only as a stand-alone piece.

3. Trust and experience

Google E-E-A-T principles are particularly important for help content. Readers need to know that the guidance reflects real product use and credible expertise.

Add:

• Author or reviewer information where suitable
• First-hand examples
• Tested workflows
• Clear update dates
• Source links for external claims
• Warnings around technical or financial consequences
• Screenshots, videos or evidence where they improve understanding

A short note such as “Reviewed against the current dashboard interface in February 2025” can be useful when it is accurate and maintained.

4. Usability and accessibility

Check:

• Short paragraphs
• Clear action steps
• Descriptive link text
• Accessible image alt text
• Tables used only where they improve comparison
• Mobile-friendly formatting
• Plain explanations for technical terms
• Error recovery instructions

A knowledge base article is successful when the reader can complete the task. Rankings matter, but task completion and reduced support demand are also important KPIs.

A Repeatable Article Production Framework with SEOLetters

A structured blog writer should support a process that your team can repeat. The following framework works for a new help centre, an established SaaS knowledge base or a large editorial site.

Step 1: Build the topic and keyword inventory

Start with several sources:

• Search Console queries
• Support ticket themes
• Sales call objections
• Product analytics
• Competitor content gaps
• Keyword research tools
• Community discussions
• Existing internal search data

Group terms by user problem rather than by wording alone. “Password reset”, “forgotten password” and “cannot access account” may belong to one support cluster, although each could require a separate troubleshooting path.

SEOLetters can help you turn keyword research into topical authority clusters, with difficulty ratings and connected content opportunities.

Step 2: Assign a content role

Every proposed article should have a category label:

• Core guide
• Supporting guide
• Feature documentation
• Troubleshooting article
• Glossary entry
• Comparison page
• Use-case article
• Template or resource page
• Content refresh

The category helps prevent a blog post from drifting into product documentation or a troubleshooting article from targeting a broad educational term.

Step 3: Check for existing URL conflicts

Before drafting, search your site for:

• The exact target keyword
• Close variants
• Existing titles
• Related slugs
• Similar H2 headings
• Internal search terms
• Pages receiving organic impressions

If a relevant page exists, decide whether the new brief should become an update, a child page, a consolidation project or a genuinely separate article.

Step 4: Generate a structured outline

The outline should include:

• Primary search intent
• Secondary questions
• Target reader
• Recommended page type
• Proposed title and H1
• H2 and H3 structure
• Internal link targets
• External evidence requirements
• FAQ questions
• Product references
• Editorial risks

This is where a structured blog writer earns its place. You can generate a consistent framework without asking every writer to start from a blank document.

Step 5: Draft with brand and product controls

SEOLetters can generate articles in a human-sounding voice tuned to your brand, with headings, links, schema and images. You can also route stages to different AI models using your own keys, which gives larger teams more control over costs, governance and model selection.

The draft should include useful detail, but it should not inflate a simple answer into an awkward 3,000-word page. Length is a secondary consideration. The user’s task comes first.

Step 6: Run editorial checks

Use an approval checklist before publication:

• Does the page answer one main question?
• Is the intended audience obvious?
• Does another URL already answer this query?
• Are the steps accurate?
• Are the links relevant?
• Are claims supported?
• Has the primary keyword been used naturally?
• Does the article include unnecessary generic advice?
• Does the page need a screenshot, table or example?
• Should an existing page be merged or redirected?

Step 7: Publish and monitor

SEOLetters supports direct publishing to WordPress, Shopify and webhooks. Once the article is live, track:

• Impressions
• Click-through rate
• Average position
• Organic sessions
• Assisted conversions
• Scroll depth
• Time to task completion
• Support ticket reduction
• Internal search exits
• Ranking overlap with related URLs

Do not judge a new knowledge base page only by traffic. A troubleshooting article may receive modest visits but save substantial support time.

For high-volume sites, set an autonomous campaign with a topic, cadence and destination. The system can research, draft and publish according to your workflow, while your team retains editorial control through the check stage.

Example: Resolving a Knowledge Base Keyword Conflict

Imagine a project management software company has these three URLs:

1. /blog/project-dashboard-guide
2. /help/project-dashboard-setup
3. /features/project-dashboard

The pages share the following terms:

• Project dashboard
• Create a project dashboard
• Project dashboard examples
• Dashboard widgets
• Project reporting

The blog article explains the general value of dashboards. The help article explains how to configure one. The feature page describes the product’s dashboard capability.

The structure may be sound, but the targeting is blurred.

Recommended repositioning

URL	Revised target	Content purpose
Blog guide	How to design an effective project dashboard	General education and planning
Help article	How to create a project dashboard in [Product]	Product-specific instructions
Feature page	Project dashboard software	Commercial evaluation and conversion

The internal links should reflect the hierarchy:

• The blog guide links to the feature page for product evaluation.
• The feature page links to the setup article for existing customers.
• The setup article links back to the general guide only where planning context is genuinely useful.

The titles, introductory paragraphs and schema should reinforce those roles. This reduces the chance of serp ranking conflicts while preserving the value of all three pages.

When consolidation is better

Suppose the blog guide and help article are both short, both explain the same setup process and neither has meaningful backlinks. In that case, creating a stronger single page may be better.

Possible actions include:

• Merge the useful sections into the strongest URL
• Add a redirect from the weaker URL
• Update internal links
• Remove the redundant page from the sitemap
• Monitor rankings and indexing after the change

Do not merge pages simply because they mention the same noun. Merge when the user intent, audience and content job are substantially the same.

Duplicate Content SEO and Knowledge Base Governance

Duplicate content SEO is often misunderstood. Search engines can handle similar pages in many cases, and not every repeated phrase is a problem. The concern is usually about wasted crawl attention, diluted signals and unclear page selection.

Knowledge bases are especially vulnerable because technical instructions often use standard language. Several pages may naturally mention the same feature, setting or error code.

Governance rules that reduce duplication

Create a content governance document covering:

• Naming conventions for features
• URL structures
• Canonical rules
• Update and ownership responsibilities
• Archive and redirect procedures
• Page type definitions
• Keyword assignment
• Internal linking standards
• Product terminology
• Review frequency

A keyword map should record the primary URL for each important topic. It should also show secondary pages that support the topic without trying to rank for the same broad phrase.

Topic cluster	Primary page	Supporting pages	Risk to monitor
Password management	Password management guide	Reset instructions, security tips, SSO help	Shared “password management” targeting
Customer onboarding	Customer onboarding framework	Checklist, email sequence, product setup	Blog and product page overlap
API authentication	API authentication guide	Token errors, OAuth setup, code examples	Technical pages competing with glossary
Invoice automation	Invoice automation overview	Workflow setup, integrations, troubleshooting	Commercial and informational overlap

The document should be updated as new content is published. Otherwise, it becomes another neglected spreadsheet.

How to Use Internal Links Without Creating More Confusion

Internal links are helpful for users and search engines, but careless linking can reinforce keyword cannibalization. If five pages all link to different URLs with the anchor text “knowledge base software”, you are sending mixed signals about the preferred destination.

Use a controlled linking approach:

• Assign one primary URL for the broad topic.
• Use descriptive, varied anchor text.
• Link from supporting pages to the primary guide where appropriate.
• Link to child pages for specific tasks.
• Avoid forcing the same exact-match anchor repeatedly.
• Review links when pages are merged or redirected.
• Add breadcrumbs and related-content modules that reflect the information architecture.

A useful model is the hub-and-spoke structure:

• Hub: Broad, authoritative overview of the topic.
• Spokes: Specific tasks, errors, examples or use cases.
• Conversion page: Product or service page where relevant.

The hub should not absorb every possible question. If a spoke has a clearly different intent, let it stand and make the relationship explicit.

Metrics and Benchmarks for a Scaled Knowledge Base

A publishing operation needs measurable standards. Page count is not enough, and keyword rankings alone can give an incomplete picture.

Suggested KPI categories

Visibility metrics:

• Non-brand impressions
• Ranking distribution
• Featured snippet ownership
• Share of search for priority clusters
• Number of queries with multiple ranking URLs

Engagement metrics:

• Organic click-through rate
• Scroll depth
• Article completion
• Internal search refinements
• Clicks on next-step links
• Return visits for unresolved tasks

Business and support metrics:

• Trial or demo assists
• Product activation
• Deflection of support tickets
• Reduced average handling time
• Documentation-related customer satisfaction
• Conversions from educational articles

Content quality metrics:

• Editorial approval rate
• Factual correction rate
• Time from brief to publication
• Refresh completion rate
• Broken-link rate
• Pages with no internal links
• Pages with overlapping primary keywords

For keyword cannibalization, monitor the number of URLs ranking for each priority term and whether one page has a stable position. A sudden change may indicate a new conflict, an algorithm update, a content-quality issue or a technical indexing change.

A practical quarterly benchmark

Every quarter, review:

1. The top 50 non-brand queries.
2. Queries with two or more ranking URLs.
3. Pages with high impressions and low click-through rate.
4. Pages losing rankings after new content launches.
5. Articles older than 12 months.
6. Help pages with high exits or repeated searches.
7. Clusters where no URL has achieved meaningful visibility.

Then assign each page one action:

• Keep and monitor
• Improve
• Expand
• Reposition
• Merge
• Redirect
• Remove
• Add internal links
• Request subject matter review

SEOLetters’ performance dashboard can support this ongoing review by connecting publishing activity with content performance. That makes refresh campaigns easier to prioritise instead of relying on a vague feeling that the site needs “more content”.

A Hypothetical SaaS Example: From 40 Articles to a Clearer Information Architecture

A customer support platform has published 40 articles around “customer service knowledge base”. Organic traffic is growing, but several pages rank between positions 30 and 70. Search Console shows that six URLs receive impressions for the same broad phrase.

The team completes a keyword cannibalization audit and discovers:

• Two introductory guides have near-identical audiences.
• Three help articles use the broad phrase despite targeting separate setup tasks.
• One comparison page is attracting informational queries.
• Internal links point to four different URLs for the same topic.

The team then:

• Merges the two introductory guides.
• Retitles the setup articles around their exact tasks.
• Rewrites the comparison page for commercial investigation intent.
• Chooses one canonical hub page.
• Updates internal links and breadcrumbs.
• Adds FAQ schema where questions are genuinely answered.
• Refreshes outdated screenshots.
• Sets a quarterly review campaign.

The outcome to monitor is not just higher rankings. It should include a cleaner distribution of queries, improved click-through rate and fewer users returning to internal search after opening an article.

That is the broader value of software-led drafting. It can help the team produce the content, but the system also supports the planning and maintenance work around it.

Common Mistakes When Scaling Article Writing Services

Publishing every keyword as a separate page

Keyword lists are not content strategies. Close variants often belong to one authoritative guide, with supporting sections or child pages where the intent justifies them.

Asking AI to “write an SEO article” without context

A generic prompt will not know your existing URLs, product terminology, audience or editorial rules. Give the writer a defined page role, target intent, internal links and factual sources.

Treating editorial review as a grammar check

Grammar is only one part of quality. Reviewers need to verify product accuracy, search intent, source credibility, differentiation and task completion.

Using canonical tags to hide weak planning

Canonicalisation can help search engines understand preferred URLs, but it does not replace a content decision. If two pages are intended for different users, clarify them. If they are the same page, consolidate them.

Ignoring old content

New articles can create conflicts with pages that have existed for years. A refresh campaign should assess old URLs before a new cluster is drafted.

Measuring output instead of outcomes

Publishing 100 articles does not prove that the knowledge base is working. Check rankings, support deflection, conversions, engagement and the number of unresolved content conflicts.

Editorial Template for a Safe SEO Knowledge Base Article

Use this template when briefing SEOLetters or reviewing a generated draft.

Article brief

• Primary keyword:
• Secondary keywords:
• Search intent:
• Target audience:
• Page type:
• Primary URL:
• Related existing URLs:
• Potential cannibalization risk:
• Unique job of this page:
• Product or service references:
• Evidence or sources required:
• Internal links to include:
• Suggested CTA:
• Review owner:
• Last verified date:

Draft structure

1. Direct answer or outcome-led introduction
2. Definition of the problem
3. Context and user impact
4. Step-by-step instructions or framework
5. Examples and edge cases
6. Warnings or limitations
7. Related resources
8. Clear next step
9. FAQ section where useful

The article should not repeat the same point in every section simply to meet a word count. If the answer is short, keep it short. If the topic involves several workflows, document them properly and make the navigation clear.

Why SEOLetters Fits a Knowledge Base Publishing Operation

SEOLetters is more than a text generator. It connects research, planning, drafting, optimisation, publishing and maintenance in one workflow, which is important when your site contains hundreds or thousands of pages.

You can use it to:

• Build topical authority clusters before writing
• Identify gaps against competing sites
• Generate structured articles with headings and formatting
• Add internal links and schema
• Produce product-aware content for software and affiliate sites
• Publish directly to your chosen destination
• Schedule recurring campaigns
• Refresh existing pages instead of continually adding new ones
• Generate content in 21 languages
• Track how published pages perform
• Route AI tasks through Gemini, OpenAI or Claude with your own keys

For a global marketing team, this can reduce the copy-paste grind between keyword selection and a live article. Your strategy and editorial judgement remain important. The repetitive production steps become easier to manage.

If you are assessing article writing services for a knowledge base, start with the SEOLetters application and examine how it fits your existing content governance, CMS and approval process.

Key Takeaways for Avoiding Keyword Cannibalization

• Every knowledge base article needs a defined search intent and content role.
• SEO keyword overlap is not automatically harmful, but unmanaged overlap creates uncertainty.
• A keyword cannibalization audit should compare URLs, audiences, page types, SERP results and content coverage.
• Duplicate content SEO issues often emerge when old pages, new drafts and product documentation are not managed together.
• Editorial checks must cover factual accuracy, user experience, E-E-A-T, internal links and information architecture.
• A structured blog writer should assess the existing site before generating another article.
• Content refresh campaigns can be as valuable as new publishing campaigns.
• Track support deflection, conversions, rankings and query distribution, not just article volume.

Build a Scalable Knowledge Base with SEOLetters

A strong knowledge base is not a pile of articles. It is a managed search and support system, with clear page ownership, sensible topic clusters and enough editorial control to keep software-led production trustworthy.

When you are publishing at scale, the main risk is not only thin content. It is strategic blur. Several pages begin answering the same question, your internal links lose direction and the search engine has less reason to favour one URL.

SEOLetters helps you bring structure to the complete process, from keyword research and competitor gap analysis to article drafting, editorial workflows, publishing and performance monitoring. Set a topic, choose a cadence and connect a destination, then let the campaign handle the production work while your team checks the important details.

If you are ready to scale SEO articles for a help centre without encouraging serp ranking conflicts, start using SEOLetters. For questions about your publishing workflow, use the rightbar as the contact path.