Generate pages

Generate a page from its Page Plan, then review facts, claims, links, metadata and language before saving, approval and supported publication.

Before you generate

Review the Business Profile, the selected Content Calendar topic, and its Page Plan first. Generated pages are stronger when the business context and page strategy are accurate.

How to generate a page

1Open the topic's Page Plan.
2Confirm the search need, page type, structure, and instructions.
3Choose the generate action in Rankvia.
4Review the resulting page, including its claims, positioning, metadata, and internal links, before publishing.

What happens next

Rankvia prepares a complete page from the plan. The page remains a reviewable result; you are responsible for final accuracy and approval before it is delivered or published.

Review an AI-generated article before publication

Review the reader’s answer, not just the spelling. Rankvia is a website-growth autopilot that can select work, prepare a Page Plan and generate a page for an eligible publishing journey. A finished draft still needs business evidence and editorial judgement. In Review First, finish that review before publication; eligible opt-in automatic publication is a separate choice, not a factual guarantee.

Annotated review: a HarborDesk rollout article

1. Check product and factual accuracy

Draft fragment: HarborDesk automatically migrates every booking system in one click.
Reviewed version: Before rollout, document the systems holding appointments and confirm the supported transfer process with the product team. This example does not establish automatic migration.
Editorial decision: Match capabilities to current, approved product documentation. When the evidence is missing, remove the claim or ask the owner to confirm it. A plausible sentence is not product evidence.

2. Remove unsupported outcome claims

Draft fragment: Cut administration by 60% and guarantee a compliant rollout.
Reviewed version: Use a responsibility checklist to make booking changes and exception handling clear before rollout.
Editorial decision: No measured saving or compliance evidence is supplied. Explain the practical purpose without inventing a percentage, certification or guaranteed result.

3. Answer the central question early

Draft fragment: Digital transformation is changing the future of every service business.
Reviewed version: Prepare a location inventory, a booking-responsibility map, a list of exceptions and an agreed review owner before introducing a shared appointment workflow.
Editorial decision: The operations lead needs a preparation checklist. Give that answer first, then explain each item with enough detail to use it.

4. Remove repetition and unrelated sections

Draft fragment: Separate sections on the future of scheduling, the future of coordination and why digital change matters.
Reviewed version: One short explanation of the rollout goal, followed by preparation, responsibilities, exceptions and review.
Editorial decision: Merge overlapping introductions. Omit the history of scheduling software unless it changes a preparation decision. Length alone does not make the article useful.

5. Treat alternatives fairly

Draft fragment: Other scheduling tools cannot support serious teams, so HarborDesk is always the best option.
Reviewed version: A single-location team may be adequately served by its current booking process. Assess HarborDesk only when shared visibility and clear responsibilities match the actual need.
Editorial decision: Do not invent competitor weaknesses or turn an incidental brand mention into a confirmed competitor. Verify equivalent capabilities before making a real product comparison.

6. Verify links and descriptive anchors

Draft fragment: Click here for a generic home page, plus a broken setup link repeated in every section.
Reviewed version: Link ‘rollout preparation checklist’ to the verified checklist and ‘supported appointment workflow’ to the relevant product explanation, if those pages actually exist.
Editorial decision: These are illustrative destination labels, not live HarborDesk URLs. Open each real destination, confirm its answer and access, and remove broken or irrelevant links. Prepared links are not proof of automatic edits to published pages.

7. Check metadata and image meaning

Draft fragment: SEO title: ‘The best compliant scheduling platform’. Image: an unverified customer dashboard.
Reviewed version: SEO title: ‘Appointment rollout preparation: responsibilities and exceptions’. Use a relevant, permitted illustration with accurate alt text, or omit an unsuitable image.
Editorial decision: Keep title, H1, description and slug aligned with the article. Check image rights, crop, rendering and alt text. Do not present an illustration as a real product screen or customer result. Review metadata separately from the body.

8. Match approved language and market

Draft fragment: An English draft for a Spanish-language site, with unexplained regional terminology and an unsupported local legal statement.
Reviewed version: Use the approved website language, terminology suited to the intended readers and neutral operational examples. Remove the unverified legal statement.
Editorial decision: The interface language does not decide the article’s publishing language or market. Check the approved Business Profile context and the actual wording. Correcting the profile does not translate a saved article automatically.

A more useful opening after review

Before rolling out appointment coordination across locations, list where bookings are recorded, who may change them and who handles exceptions. Give each location a named review owner and agree how unresolved cases reach the central team. Confirm the supported product workflow before promising any transfer or automation. If the current process already meets these needs, a new tool may not be necessary.

Apply the review in the existing article editor

1. Open the saved article and read the preview
Open the generated result from its topic. Compare the preview with the Page Plan and approved business context. Record specific corrections and the evidence behind them; do not approve a claim merely because the article appears complete.
2. Make direct edits and save them
Use the Markdown editing mode for precise body changes, preview the result and save. Saving a changed body creates a saved version; cancelling unsaved edits retains the saved content. Metadata has its own edit/save controls for the available title, H1, slug, SEO title, description and excerpt. Check the hero image and its available alt-text controls separately.
3. Use Improve only when a revision is useful
The existing Improve control accepts specific revision notes and can create another article version. Give concrete requirements, such as removing an unsupported migration claim and retaining the preparation checklist. Re-read the returned version; submitting notes is not approval. It is a generation action subject to existing eligibility and usage rules, not a free factual-verification service.
4. Confirm the saved version, then choose publication
Save body and metadata changes before approval, export or publication. A manual body edit to an approved draft returns it to draft status, so review it again. Use the approval control when offered, then follow the connected WordPress/Shopify or manual-export instructions. Approval and publication are separate actions; check the destination, state and resulting page. Do not use a live publish action merely to test the editor.

Editorial responsibility and product validation are different

Rankvia performs deterministic content checks and enforces permissions, saved-result usability and publishing prerequisites. These checks can surface structural or rule-based issues; they do not independently establish that every statement, competitor claim, source or regional assumption is true. A completed generation is not an editorial sign-off.

The human review above checks relevance, evidence, fairness, working destinations, image suitability and language/market fit. Follow any review notes shown in the article. Keep unresolved factual claims out of the approved version. No quality score, ‘humanisation’ label or automatic publishing option replaces that decision.

APPLY THIS TO YOUR WEBSITE

Start with the website decision before the draft

New to Rankvia? Use the existing Search Growth Plan flow. Authentication, eligible website analysis and Business Profile approval precede planning. Rankvia can decide what to create or improve; a reviewed article is a later step, not an instant arbitrary-text assessment.

Build my free Search Growth Plan

This action starts planning. It does not approve or publish an article.

Still need help?

Contact Rankvia support with the website and task you were working on. Do not include passwords or other credentials.

Contact support →