Pattern 1: Bulk content refresh
Use this pattern to recover decaying pages at scale. Start from your existing performance data and move straight into execution without manual context-gathering.1
Surface your candidates in Pages
Go to Pages and apply the Decaying traffic filter to surface URLs where clicks or rankings are trending downward. You can combine this with an AI visibility filter to prioritize pages also losing citations.
2
Send URLs to a Sheet
Select all filtered URLs and click Send to Sheet. VeluraHQ creates a new Sheet pre-populated with those URLs and their performance metadata — no CSV export needed.
3
Add a Deep Refresh workflow column
Click the + column header, choose Workflow, and select your Deep Refresh workflow. Map the URL column to the workflow’s
page_url input field.4
Add a CMS Output column
Add a second Workflow column configured to push approved drafts to your CMS — Webflow or WordPress. This column activates only after a row clears review, so no draft publishes automatically.
5
Set your quality threshold and review gate
In the workflow column settings, configure the quality score threshold that triggers a human review hold. Rows above the threshold pass through; rows below land in the Needs Review queue for manual inspection.
6
Run all rows
Click Run all. Monitor batch progress in the progress bar and the Run activity panel. When the batch completes, open the Needs review filter to process gated rows.
7
Approve and publish
Bulk-approve rows that meet your quality bar. Handle exceptions individually — inspect the per-row log, adjust the content or inputs, and re-run the row. Approved rows push directly to your CMS through the output column.
Pattern 2: Programmatic page generation
Use this pattern to launch templated content — comparison pages, glossary entries, location pages, tool pages — at scale from structured inputs.1
Prepare your structured input CSV
Build a CSV with one row per page and a column for each template variable:
topic, target_keyword, template_type, and target_url_slug. Clean, consistent column names make input mapping easier in the next step.2
Import the CSV into a new Sheet
Go to Sheets, create a new Sheet, and use Import CSV to load your file. Verify the column headers and row count before proceeding.
3
Add a template workflow column
Click + to add a Workflow column and select your page generation workflow. Map each workflow input to the corresponding Sheet column — for example, map the
target_keyword column to the workflow’s keyword input.4
Add a Quality Score column
Add a SuperBlock column using the AEO Quality Score SuperBlock. This column runs automatically after the generation step and attaches a score to each row, measuring brand alignment, structure, and citation readiness.
5
Run all rows and triage by score
Click Run all. Once the batch completes, sort by quality score. Bulk-approve rows above your threshold; open the per-row log for rows below threshold to diagnose and fix the issue before re-running.
6
Publish approved rows to your CMS
Select all approved rows and use Bulk publish to push them to WordPress or Webflow in a single action. Rows not yet approved remain in the Sheet until you clear them.
Controlling quality at scale
Running workflows across thousands of rows means quality variance is inevitable. Use a layered approach to catch issues before they reach your CMS:- Automated quality scores — Add a Quality Score SuperBlock column to every Sheet that generates content. Scores measure brand alignment, structural completeness, and citation readiness for each row automatically.
- Manual review for high-stakes content — Set a lower quality threshold for high-traffic pages or new content types so more rows land in the Needs Review queue for human inspection.
- Per-row logs for diagnostics — Every row keeps its own execution log. When a row fails or scores unexpectedly low, open the log to see exactly which step produced the issue and what the inputs were.
Credit planning for bulk runs
Large Sheet runs can consume a significant portion of your monthly credit allocation. Plan ahead to avoid interruptions:- Check estimated cost before running — When you configure a Workflow column, VeluraHQ shows an estimated credit cost per row. Multiply by your total row count for a batch estimate before committing.
- Run a 50-row sample first — Use a sample run to validate both quality and actual credit consumption before scaling. Estimated and actual costs can diverge depending on workflow complexity.
- Schedule large batches for off-peak hours — Use the Automation panel to run large batches overnight or over the weekend. This keeps your daytime credit budget available for manual, interactive work during business hours.
Failed rows don’t consume a second credit allocation automatically. When a row fails, it stops executing and is not retried until you trigger a manual retry. Fix the underlying issue first — incorrect input data, a misconfigured mapping, or a workflow error — then re-run the failed rows individually. You control when credits are spent on retries.