• Content · Search Console

Content plan: what pages to write, in what order and when to stop

Our content plan looks like a queue table: a line is the future page, the line has a responsible person, format, acceptance criteria and date. At the entrance there are two lists: what has already been published and what is missing by demand. The output shows the order in which it is written and the number after which we stop writing. The order is calculated from three values ​​at once: demand, the distance of the page to money and the cost of its production. The line, which only the first one is known, does not get into the queue - that is where the plans come from, where articles are written for three months, to which the catalog has no relation. The first lines of the queue are almost always among the already published. In the watering shop we measured, five sections of services are menu items, and the content of each is a duplicate heading: it is cheaper to add them than to start new ones. The term is 8–25 working days, depending on the number of directions. The price is after a free analysis of the existing one.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
What's out
queue of pages: responsible, format, acceptance criteria, date
Price
after a free audit
Guarantee
30
days after project sign-off
What's out
queue of pages: responsible, format, acceptance criteria, date
Term
8-25
working days: calculated by the number of directions, not by the size of the site
Before the estimate
free analysis of existing content, 2-4 working days
Measured find
5
sections of services in the menu with a duplicate title instead of text, measurement 08/01/2026
Measured proportion
590
addresses in the spice shop, of which 3 are informative
What we do not promise
of traffic and items to date: the plan specifies the order of work, not the behavior of issuing
What's included

Complete list of work and what you get as a result

  • Inventory of published: address, type of page, amount of text, impressions for the last three months
  • A summary list of the required pages with a division into three states: exists and works, exists and is empty, and does not exist at all
  • The order of the queue is based on three values: demand, the distance of the page to the money, and the cost of its production
  • The rate per month is calculated from the hours of your specialist, not from the desired number of publications
  • Format and acceptance criteria for each type of page: what must be in the text to be counted
  • Binding of each line of the queue to the page from which it will be internally linked
  • Check for competition with existing pages before enqueuing the row
  • The stop criterion, written in a number: at what indicator the queue stops and the work switches to strengthening the existing one
  • The order of monthly review of the queue and the rule of what to do with the missed month
  • The document itself: a table with responsible, dates and criteria, according to which your copywriter can work without us
When this service isn't right

What's not included — so there are no surprises at delivery

  • Writing the pages themselves is a separate work, counted piece by piece
  • Collection and clustering of queries: the plan works with ready-made semantics, and if it is not, it is a previous stage, not this one
  • Management of social networks, newsletters and videos: the plan applies to the pages of the site
  • Design and layout of templates for new types of pages
  • Not suitable for a site with one or two pages: there is nothing to organize there, a queue of three lines is stuck in the head
  • Not suitable if there is no one inside the company to confirm the actual part of the texts: the plan will be made, but it will not be carried out
Who it's for

Situations where this service delivers results

Scenario 1 of 4

The semantics are collected, but the work does not move

There is a file with clusters and a list of missing pages, but it is not clear where to start. The plan turns the list into a queue with dates and responsibles: each line has a writer and a receiver.

We'll review your situation in a free audit
Free audit

Free analysis of existing content

We look not at what you plan to write, but at what has already been published and in what state it is. The analysis is external: access is required for two items out of six, the rest is taken from what the site gives to everyone. The most frequent result is that the first lines of the future queue are among the already existing pages and cost less than the new ones.

What we measure

  1. How many pages are published and what type are theyWe count unique addresses and divide them into categories, cards, information and service. In the spice shop, such a calculation gave 590 unique addresses: 7 categories, about 580 product cards and exactly 3 information pages.
  2. How many of them are empty or filled with stubsA page in the menu is not yet a page with text. In the irrigation system store, 5 service sections exist as menu items, and the content of each is a duplicate title and nothing else.
  3. How much of what is published gets impressionsAccording to the Search Console report by pages. This number divides the available into two parts: what is worth strengthening, and what is pointless to add.
  4. Are there pairs of pages competing for the same request?Two pages for one need eat each other before you add a third. Such pairs are checked before enqueuing new rows, not after.
  5. Does the search engine see what is already written?We compare the site map with the live list of addresses. In the store we measured, all 590 addresses of the map led to one language version, and the second one was not in the map at all - writing new texts for it would be an expense without consequence.
  6. Who writes and how many hours are actually available for itThe main limitation of the plan is not the budget, but the person who proofreads the actual part. The rate for a month is calculated from its hours.

What you get

  • Available content in numbers: how many pages, how many of them are empty, how many are getting impressions.
  • A list of pages that are cheaper to add than to create new ones.
  • Pairs of pages competing for the same requests.
  • Estimate the rate per month for your real resource.
  • A 30-minute conversation on the document, where you can argue with the conclusions.

Timeline: 2-4 working days

Why is it free

Because after analysis, part of the customers understand that it is not necessary to write something new yet - first you need to add the existing one, and it is twice as cheap. It is a pity for both parties to lose a paid month of queue on this.

What's next

Next, we compile the queue itself: order, norm, acceptance criteria and stop rule. Pages are written individually and piece by piece - you can pick up the queue and give it to your copywriter.

Short form: your contact and site URL
Contract and paperwork

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

  • Number of directionsThe demand is checked separately for each direction, so the volume of analysis grows from their number, and not from the number of pages on the site. A store with two sections and a service site with a dozen directions are different in terms of work intensity with the same number of addresses.
  • Does what has already been published measure up?If Search Console and analytics are in place, inventory is done by reports. If not, it is necessary to remove the condition with an external measurement, and these are separate days. In the store of irrigation systems, we recorded a complete absence of measurement systems: there is no place to get "what works" at all, only an external assessment remains.
  • Queue depthThe queue for the quarter and the queue for the year differ not in the length of the table, but in the number of checks: for distant lines, the demand has to be checked again, because it changes in six months.
  • How many types of pages are in the workEach type has its own acceptance criteria: what makes a product card suitable does not make a service page suitable. The five types are five separate agreements about what counts as completed work.
  • The state of indexing at the startIf the sitemap doesn't have an entire language version — like in the measured spice store, where all 590 addresses led to one language — technical edits become the first lines of the queue, and the plan has to be reconciled with the technical queue. This adds alignment, but saves money on text that a search engine wouldn't see.
Cases

Tasks and results in numbers — all metrics measured by us

Greenter

a store of automatic and drip irrigation systems with landscape services, a catalog of 300 items

Task
Understand where the content queue should start in a store with a catalog of 300 items in 40 categories.
Solution
Instead of a survey, there is an external dimension: traversal of the root categories by pagination, reconciliation with the output of an internal search for 18 different queries, separate checking of service and information pages and what is written on them.
Result
Measurement 01.08.2026: the first lines of the queue were found among the already published. 5 pages of landscape services are menu items, and the content of each is a duplicate title and nothing else. 2 out of 5 root categories return "no products". On the combat site, there are still stubs of the topic: the description of the site "My Shop", the delivery section with the text "Description of delivery conditions", the services section - "There will be information here." Catalog measured by two independent methods with 0% variance: 300 products in 40 categories.

a brand of natural spices and seasonings with its own online store

Task
Calculate the proportion between commercial and non-commercial pages before planning the volume of texts.
Solution
Analysis of the site map with the calculation of unique addresses and division into categories, cards and information pages; separate reconciliation of language versions with markup.
Result
Measure 07/31/2026: 590 unique addresses — 7 categories, about 580 product cards and exactly 3 information pages. That is, all the non-commercial content of the store is three pages. Recently, something was found that changed the order of the work: the site map is inflated to 3,971 entries for the same 590 addresses, and all of them lead to the Russian version — there is no Ukrainian-language version in the map at all, although hreflang uk is announced. Queuing texts for a version that is not in the map would be a waste of time.

Pancer Protection

online store of tactical and military equipment with a catalog of more than 50,000 SKUs

Task
Determine the limit of manual work on the catalog of more than 50,000 items.
Solution
Calculating the volume using two independent methods — analysis of the sitemap index from 32 product files and cross-checking with standard search.
Result
Measurement 07/31/2026: 54,302 products and 635 categories, a total of 110,096 addresses in two languages; the discrepancy between the two methods is 0.4%. In the same calculation, there are 1,270 category addresses, 210 informational and 12 custom pages. First server response 413.8ms: The volume itself is not the problem, the problem is how to fill it. The top is written individually here, the rest is covered by rules for page types.

Did not find your case?

Describe how it works on your side — we will tell you whether “Content plan for semantics” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Total duration:8–25 days

  1. Inventory of the published

    2-4 working days

    We collect a list of all pages with the type, volume of text and impressions for three months. We mark the empty ones separately: a page in the menu and a page with text are different things, and the difference is visible only in such a list.

  2. Reconciliation of the list with the demand

    2-5 working days

    We impose clusters of requests on existing addresses. There are three states at the output: the page exists and works, exists and is empty, and does not exist at all. Next, each state has its own cost of work, and this is where the real volume becomes visible.

  3. Prioritization and rate per month

    1-3 working days

    We calculate the order by demand, distance to money and production cost, after which we divide the hours of your specialist by the average time of one material. The resulting norm is almost always less than expected - and it is precisely this that is fulfilled.

  4. Acceptance criteria and formats

    1-4 working days

    Under each type of page, we record what should be in the text for the work to be counted: mandatory questions, tables, who confirms the actual part. Without this acceptance turns into a dispute about taste.

  5. Intersection check and link map

    1-4 working days

    We check each line with existing pages for competition for the same request, and then we determine where the link to the new page will be from. A page without incoming links remains an island even in a perfect queue.

  6. Stop and transfer rule

    1-3 working days

    We write down the number at which the queue stops and agree on a monthly review based on actual readings. Next, we give the table and go through it together with the person who will work on it.

Technologies & integrations

What we build on and what it connects to

Stack

  • Search Console: report by pages and queries
  • internal site search
  • Screaming Frog - traversal of existing pages
  • reconciliation of the site map with the live list of addresses
  • GA4
  • queue table with responsible, dates and acceptance criteria
  • checking page-request pairs for competition

Integrations

  • Google Search Console
  • GA4
  • internal site search
  • Site CMS
A queue with a stop rule against "writing while writing"

How this option differs from the alternative

Stream order of texts by volumeOur approach
Order unita thousand characters, in which the goal is not set by anythingpage with acceptance criteria and assigned target
What sets the orderby what was mentioned at the meeting, or by the order of the categories in the menucalculation: how much demand, how close to payment, how much it costs to make
Volume per montha figure from a commercial proposal, disrupted for the second monthcalculated from the hours of a specialist who proofreads texts
When we stopwhen you run out of budget or patienceaccording to the agreed number: a share of the published without any impressions
What remains after worka folder with texts and questions about what to write next monththe table according to which your copywriter works further without us
What we need from you

We can't start without this — best to prepare in advance

  1. Access to Search Console. Without it, it is impossible to distinguish between a working page and one that is simply published — an external assessment of demand with the appropriate accuracy remains.
  2. List of directions with a mark, which of them bring money. The queue is based on this, not on the number of requests.
  3. An honest figure of the resource: who writes or at least proofreads and how many hours a week they have. The inflated figure breaks the plan in the second month.
  4. Accessing CMS or offloading existing pages — so inventory relies on a list rather than memory.
  5. One person has the right to approve the queue. The queue, agreed upon by the three departments in turn, turns into a wish list.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ

Most frequently asked questions — with concrete answers

How does the content plan differ from the semantic core?

Semantics answers the question of which pages should exist. The plan answers the question of the order in which they will appear, who will write them and by what criteria you will accept them. A list of two hundred clusters without a queue turns into a document that is opened once and never opened again.

How many pages should be laid out per month?

As much as your proofreader can handle the actual part. We calculate simply: divide the hours per month by the average time of one material of your type. A two-page rate every month yields more than a ten-page rate that breaks on the second month.

By what criterion to stop?

We agree on the number at the start. The rule of thumb is this: if more than half of the new pages haven't received any impressions after 12 weeks of publication, the queue stops and the budget shifts to boosting the ones that have received impressions. A site map for tens of thousands of addresses does not mean tens of thousands of pages in the index - this is directly written by Google itself.

Where to start: new pages or existing ones?

Almost always from available. Adding a page that already has an address, link and age is cheaper than creating a new one from scratch. In the irrigation system store we measured, the first five lines of the queue were found among the published ones: the service sections were in the menu, and there was no text on them - only a duplicated title.

We have a catalog of tens of thousands of items - a plan for each card?

No. At the tactical equipment store, we measured 54,302 products and 635 categories - something that is never written by hand. In a plan of this scale, there are two layers: rules for typical pages, which close the volume, and a piecemeal queue at the top - the categories and items that generate revenue.

Will the new pages start to compete with the old ones?

There is such a risk, so each line is checked for intersection with existing pages before being queued. If there is an intersection, the solution is one of two: either the line does not start, or the existing page is rewritten for another need. Two pages for one request share signals and both sit lower than one could.

Can I give the plan to my copywriter?

This is what it is made for. The output is a table with the person in charge, format, acceptance criteria and date for each line. We either write according to it ourselves, or we don't: the plan does not bind you to us as an executor.

The plan is drawn up for a quarter - what if everything changes?

The queue is reviewed once a month according to the actual numbers: we develop what has received impressions, what has not - we do not add it. The missed month is not added to the next one: the lines are simply shifted, because the double norm breaks down as reliably as the overestimated one.

When will the numbers be visible according to the plan?

The first impressions on a new page are usually visible in 6-12 weeks, and this is not the time of the result, but the time of the first signal. Moreover, according to GA4 and Search Console, a trend can be seen, not an accounting truth: blockers, consent mode, and browser restrictions on cookies eat up part of the data. We do not promise items and traffic by the date - the plan specifies the order of work, not the behavior of issuing.

Demo

Your catalogue on a phone screen

This is how your store can look on a phone: a collection banner, popular products and a cart one tap away. Tap “Add to cart” and the counter in the header updates, just like in a real store.

  • Collection bannerThe first screen shows what is new, not a logo.
  • Product cardsPhoto, price and a button — no extra page to open.
  • One-tap cartThe counter in the header updates instantly, like in a real store.
Stores in the portfolio
This is a demo interface, not a client's store. Live projects are in the portfolio.
SHOP
New collectionAutumn / WinterExplore
PopularAll products ›
  • Essentials Hoodie1 290 ₴
  • Urban Backpack1 490 ₴
  • Classic Cap690 ₴
  • Basic Tee590 ₴
  • Street Sneakers2 390 ₴
  • Active Shorts890 ₴

Send the site address - we will see what is already published on it and how much of it works.

In response: available content in numbers, a list of empty pages, pairs competing for one request, and an estimate of the rate per month for your real resource.

From measured casesMeasurement 01.08.2026: the first lines of the queue were found among the already published

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.