Programmatic SEO page scheduler
A programmatic SEO page scheduler that publishes at the pace you can review
For agencies and site owners with hundreds of approved rows. Queue them once and PageForge Pro publishes up to your daily limit in the background, retries failures and shows what went live. No 500-page launch you cannot check.
- Included from the Starter plan
- A daily limit you set
- Failed rows retry automatically
The big-bang launch
Publishing 600 pages at once leaves no time to catch a mistake
A wrong phone number in the template or a broken column reaches every page in the same minute. Spread the release out and the first day’s pages show you the problem while it is still small.
Publishing everything at once
- Every page goes live in one run, mistakes included
- Nobody can read 600 pages on the day they publish
- A browser tab has to stay open until the run finishes
- Hub pages and links lag behind the pages they should list
With the Pro scheduler
- Rows wait in a queue and publish up to a daily limit
- Each day’s pages are few enough to read properly
- The work runs in the background on WordPress cron
- Hub pages list each group as it goes live
How it works
From approved rows to a steady release in four steps
01
Prove the template first
Generate a handful of rows as drafts with an instant run and fix what you find. A schedule controls timing. It does not make a page ready.
02
Turn on the scheduler
In PageForge > Settings, enable Daily Scheduler and set a Daily Limit: the number of pages that may be generated successfully per day.
03
Queue the campaign
On the Generate screen, set Mode to Queue (Scheduler), run Check and preview, then click Queue N rows for the scheduler.
04
Watch it go live
The Generation Campaigns panel counts done, live, waiting and problem rows. Read each day’s pages as they publish and pause if something is off.
PageForge Pro scheduler
Background publishing you can see and stop
The queue and scheduler are part of every PageForge Pro plan, starting with Starter. Rows live in their own database table and run one at a time.
Why drip publishing
Release at the speed you can check
A steady pace gives you time to read yesterday’s pages before today’s set follows. New URLs arrive over days instead of in one burst, so hub pages and links can keep up. It will not make pages rank faster on its own. What it gives you is control.
- Catch a template error on day one, not after 600 pages
- Match the daily limit to what your team can review
- Add hub and nearby links as each group goes live
Failures without guesswork
Every row ends up done, retrying or explained
Background work fails sometimes: a host times out, a permission is missing, a URL is already taken. The queue keeps a record of each row, retries what can succeed and explains what cannot.
- Failed rows retry automatically with growing delays
- Skipped rows show why: a duplicate URL, a hand-edited page or another template’s page
- Cancelling a campaign removes its waiting rows at once
Sheets on a schedule
Keep pages in step with a Google Sheet
On the Professional and Enterprise plans, link a template to a Google Sheet and choose an hourly, twice-daily or daily sync. Changed rows go into the same queue and follow the same daily limit.
- Preview (dry run) shows a sync before you apply it
- Removals wait until one sync is previewed and applied by hand
- A sheet that comes back empty is reported as a failure
Compared
Three ways to release a large page set
Each has its place. Only one combines a steady pace with no per-page work after setup.
| PageForge Pro queue | Publish all at once | Schedule each post by hand | |
|---|---|---|---|
| Pages go live over days | Yes | No | Yes |
| Work per page after setup | None | None | Set a date on each post |
| Daily limit across the queue | Yes | No | No |
| Runs without a browser tab open | Yes | No | Yes |
| Failed rows retried | Automatically | Rerun by hand | Not applicable |
| Stalled work recovered | After 15 minutes | Resume by hand | Not applicable |
| Edit a row before it publishes | Yes | No | Yes |
| Where it is available | Pro, Starter and higher | Free and Pro | WordPress itself |
How to schedule programmatic SEO pages at scale
When a campaign has a few dozen pages, you generate them, read them and publish. When it has several hundred, publishing them all in one run means nobody reads most of them before visitors do. A scheduler fixes the timing: rows wait in a queue, and a set number go live each day.
In PageForge Pro, that is the queue and the Daily Scheduler. You queue a campaign once. A background process works through it, generates pages up to your daily limit, retries rows that fail and records what happened to each one. The pages are ordinary WordPress content, created with the template, status and SEO fields you chose.
Note: The queue, scheduler and drip publishing are included in every PageForge Pro plan, starting with Starter. The free plugin generates in your browser while the Generate screen is open, up to 100 rows per run, and has no scheduler.
A scheduler controls timing, not readiness
A queue will publish a broken page on schedule just as reliably as a good one. Scheduling comes after the template, the data and the review process are proven, never instead of them. Every safeguard on this page assumes the first drafts have already been read by a person.
Why drip publishing matters
Drip publishing spreads a campaign over days or weeks. The reasons are practical:
- Review capacity. Your team can read 10 or 20 new pages a day. Nobody reads 600 in an afternoon. A daily limit matches output to the attention you actually have.
- Smaller mistakes. A wrong phone number in the template or a column shifted by one reaches the first day’s pages, not the whole campaign. You fix it while it is still small.
- Crawl pacing. New URLs arrive in steady groups rather than one burst. That can make discovery easier to follow in Search Console, but it is not a ranking lever, and no plugin can promise rankings or indexing.
- Links keep up. Hub pages, related links and navigation can grow with each group instead of trailing behind a sudden flood of pages.
- Readable results. Pages released in groups are easier to compare. You can see whether the first region’s pages get impressions before you queue the next.
Before you queue anything
Prove the pages first. Use an instant run, or the free plugin, to generate a handful of rows as drafts, and check them:
| Check | What to look for |
|---|---|
| Placeholders | No {City} text anywhere, including buttons and footers |
| Facts | Prices, phone numbers, hours and areas are right |
| SEO fields | Title and description in your SEO plugin match the page |
| Schema | Business type, city and country are correct |
| Mobile layout | Long names do not break headings or buttons |
| Links | A hub exists for the pages, and related links resolve |
Then run Check and preview on the full file. It reports how many pages will be created, updated or skipped, shows the first page’s title and URL, and stops the run if a title or slug placeholder has no matching column. See Quality checklist before you publish and Check and preview.
Set up the scheduler
Open PageForge > Settings in PageForge Pro and set:
- Enable Daily Scheduler. Processes queued rows with seven checks a day, in your site’s timezone as set under Settings > General.
- Daily Limit. How many pages may be successfully generated per day.
Rows that are skipped or fail do not count toward the daily limit. If a check finishes before the limit is reached and rows are still waiting, PageForge schedules follow-up runs until it is. The limit covers everything in the queue, including rows that a Google Sheets sync adds.
Tip: The scheduler runs on WordPress’s built-in cron, which fires when your site gets visits. On a quiet site, ask your host to trigger WordPress cron from a real server cron job so checks happen on time.
Queue a campaign
- On the Generate screen, choose the template and data source.
- Set Mode to Queue (Scheduler).
- Choose the post status. Publish gives you drip publishing. Draft or Pending Review queues pages for a person to approve.
- Click Check and preview and read the result.
- Click Queue N rows for the scheduler.
The rows enter the queue as one campaign. The Generation Campaigns panel on the Generate screen tracks it:
| Count | Meaning |
|---|---|
| Done | Rows that have been resolved |
| Live | Pages that are published |
| Active | Rows still waiting in the queue |
| Issues | Failed or skipped rows that need a look |
A worked example
An agency has 240 approved rows for a home services client: 60 service and city pages in each of four regions. It sets the Daily Limit to 12, so the full campaign takes about 20 days.
Day 0. The agency generates five rows from the first region as drafts with an instant run and reads them. It publishes the region’s hub page. It queues the first region’s 60 rows with the status set to Publish.
Day 1. Twelve pages go live. The account manager reads all twelve and finds that the template’s footer shows last year’s opening hours.
The fix. The agency turns off Enable Daily Scheduler, so the queued rows wait. It corrects the template. Rows still in the queue are built from the template as it is when they run, so they will pick up the fix. For the twelve published pages, it uploads a CSV with just those twelve rows and runs it with Update it from the CSV and current template, which refreshes the pages that template generated. Running the full file would create the waiting rows straight away, so it keeps the update file small. Then it turns the scheduler back on.
Days 2 to 5. The rest of the first region publishes, twelve a day. The hub lists each group as it goes live.
Day 6 onward. The second region is queued only after the first region looks right. The agency repeats this for each region and compares how each group performs before raising the limit.
The agency never had more than twelve unread pages on the site.
The Queue screen
Open Queue in the PageForge navigation to see waiting rows:
- Edit changes a row’s values or post status before it runs.
- Run generates one row right away, without waiting for the scheduler.
- Process Next N Now runs the next group of queued rows right away. N matches your daily limit.
- Clear All empties the queue.
Editing a queued row respects the editor’s publishing rights, so an account that cannot publish cannot queue a row that the scheduler later publishes. Removing rows, clearing the queue and cancelling a campaign need Editor-level access.
Failures, retries and recovery
- Failed rows retry automatically, with a longer delay after each attempt, up to an attempt limit. The Failed and skipped rows list shows the reason, the number of attempts and when the next attempt is due. Retry now tries a row straight away.
- Skipped rows are not retried, because they cannot succeed as they are: a duplicate URL, a page edited by hand, or a page another template generated. Fix the row or the template, then retry.
- Stalled rows are recovered. If a background run dies partway through a row, that row returns to the queue after 15 minutes.
- Cancelling stops the campaign straight away. Its waiting rows are removed, and a run already in progress does not write cancelled rows back.
If the same failure repeats across many rows, stop and look. Turn off the scheduler, find the cause in the failure list or your server’s error log, fix it, then let the queue continue.
Who the rows run as
Queued rows run one at a time as the user who queued them. Background pages therefore get the same permissions and the same SEO title, description and social fields as an instant run. If that account is deleted, its rows fail with a clear message in the failure list instead of creating pages without SEO fields.
Release in an order that makes sense
The queue works through rows in the background. You control the order by what you queue and when:
- Hubs first. Publish parent and hub pages before the pages beneath them. A child page cannot point to a parent that does not exist yet. See Parent pages and URL hierarchy.
- One group at a time. Queue one region, service or page family, let it finish, check it, then queue the next.
- Highest value first. Start with the markets or services that matter most to the business, so the pages you review most closely are the ones that count.
Scheduled Google Sheets sync
On the Professional and Enterprise plans, a Google Sheets sync keeps pages in step with a sheet your team edits. Choose Off (Sync now only), Hourly, Twice daily or Daily. New and changed rows go into the same queue and follow the same daily limit.
Click Preview (dry run) to see what a sync would do before you apply it. Scheduled syncs remove nothing until one sync has been previewed and applied by hand, and a sheet that comes back empty is reported as a failure rather than treated as “remove every page”. See Google Sheets sync.
Without Pro
The free plugin has no queue or scheduler, but you can still release gradually:
- Generate up to 100 rows per run, in small batches with live progress and resume. See Batches, progress and resume.
- Split a large list into CSV files of up to 100 rows, for example one per region, and run them days apart.
- Generate as Draft or Pending Review, then publish by hand after review.
- For a page that must go live at an exact time, use the Schedule option in the WordPress editor.
This works for smaller campaigns. Once you are splitting files every week or waiting on an open browser tab, the Pro queue saves real time.
Where scheduled releases fit
- Multi-location rollouts. Publish branch, city or franchise pages region by region while local owners review the first releases. See multi-location franchises.
- Agency calendars. Queue each client’s campaign at a pace their reviewers can keep up with. See agencies.
- Directories. Release listing and category pages in groups as the data is verified. See directories.
- SaaS launches. Release feature and integration pages alongside product announcements.
- Seasonal ecommerce pages. Queue buying guides and collection pages ahead of a season.
- Large refreshes. Push data changes through a sheet sync in controlled groups instead of all at once.
Safeguards
- Never let a schedule replace review. Only queue rows from a template whose drafts a person has read.
- Use one timezone. The scheduler follows the site timezone under Settings > General. Check it before you plan release days.
- Make cron reliable. Test that scheduled checks actually run on your host before you depend on them.
- Pause on repeated failure. One failed row is noise. Ten with the same reason is a template or data problem.
- Verify the first group live. Open the published pages, not just the drafts: caching, canonical tags and hub listings only show up there.
Who should use the scheduler
A strong fit is a team with validated templates, hundreds of approved rows, a hub structure ready, reliable cron and someone who reads each day’s pages.
Publish immediately instead when the release is small, fully reviewed and every page can be checked the same day. Compare editions on Free vs Pro and plans on pricing.
Use cases
Blueprints with a sample CSV included
{Service} in {City}, {State}Run a proven page structure for each client, with their own data, design and sign-off.5 clients × 6 services × 20 towns = 600 pages across 5 sitesSee the blueprintMulti-location brands and franchisesLarkfield Fitness {Location}, {City}A page for every location with its own hours, phone, amenities and directions.45 locations × 1 page = 45 pages, refreshed from one spreadsheetSee the blueprintDirectories and listing sites{Category} in {City}, {State}Category and city pages for directories, published only where you have real listings.8 categories × 60 cities = 480 possible pages, published only where listings existSee the blueprintReviews
What people say after their first campaign
Great plugin for programmatic SEO
PageForge makes programmatic SEO surprisingly easy, helping us generate scalable, well-structured pages much faster.
Using PageForge?
Reviews on WordPress.org help other site owners decide, and tell us what to build next. Good or bad, we read every one.
Write a reviewCan PageForge schedule pages?
Yes, in PageForge Pro from the Starter plan. Queue a campaign, enable the Daily Scheduler and set a Daily Limit. The scheduler checks the queue seven times a day in your site’s timezone and generates pages up to the limit. The free plugin generates in your browser while the Generate screen is open, up to 100 rows per run, and has no scheduler.
What is drip publishing?
Drip publishing spreads a campaign over time. Set the post status to Publish and choose a daily limit. With 200 rows queued and a limit of 10, the scheduler publishes up to 10 pages a day until the queue is empty, which takes roughly 20 days.
How many pages should I publish per day?
There is no number that suits every site. Base it on how many pages your team can actually read each day, how ready your hub pages and links are, and how much new content the site usually gets. Start low, check the first days’ pages, then raise the limit.
Does drip publishing improve rankings?
Not by itself, and no plugin can promise rankings or indexing. A steady pace gives you control: time to review pages, catch a template problem early and add hub links as each group goes live. Results still depend on page quality, search demand and your site.
Does WordPress cron need to work?
Yes. The scheduler runs on WordPress’s built-in cron, which fires when your site gets visits. On a quiet site, checks can run late. Ask your host to trigger WordPress cron from a real server cron job so the checks happen on time.
What happens when a row fails?
It retries automatically, with a longer delay after each attempt, up to a limit. The Failed and skipped rows list shows the reason, the number of attempts and when the next one is due, with a Retry now button. Skipped rows, such as duplicate URLs, are not retried until you fix them.
Can I pause or stop a campaign?
Yes. Turn off Enable Daily Scheduler in Settings and queued rows wait until you turn it back on. Cancelling a campaign removes its waiting rows straight away, and a run already in progress does not write cancelled rows back. Cancelling needs Editor-level access.
Can I set an exact publish date for each page?
Not per row. The scheduler works through the queue up to your daily limit rather than to dates you set for each page. For a page that must go live at a specific moment, generate it as a draft and use the Schedule option in the WordPress editor.
Do scheduled pages get the same SEO fields?
Yes. Queued rows run as the user who queued them, so background pages get the same permissions, SEO title, description and social fields as an instant run. If that account is deleted, its rows fail with a clear message instead of creating pages without SEO fields.
Which plan includes the scheduler?
Every PageForge Pro plan: Starter for one site, Professional for five sites and Enterprise for unlimited sites. Professional and Enterprise also add Google Sheets sync, which feeds changed rows into the same queue. Current prices are on the pricing page.
Publish your next campaign a day at a time
Prove the template with the free plugin, then queue the full set in PageForge Pro and let the scheduler release it at the pace you choose.
