---
title: "Optimise a page for a target keyword"
url: https://qelvra.in/playbooks/on-page-optimisation
published: 2026-11-12
updated: 2026-11-12
tokens: 1482
---

# Optimise a page for a target keyword

**On-page optimisation** (Create & optimise): An exact plan for one page: title, H1, structure, missing subtopics, internal links.

Give the agent one page. It reads the page, its searches and Google's top 10, then writes a new title, meta description, H1 and outline. Free plan.

[Start this playbook free](https://qelvra.in/app?ask=Optimise%20a%20page%20on%20%7Bsite%7D%20for%20its%20target%20keyword): the first prompt is filled into Qelvra's chat after you sign in, and nothing runs until you press send.

At a glance:
- Search Console: Helps. Works without it. Connected, the agent adds your own clicks, impressions and positions to the answer.
- Plan: Every plan, free included.
- Smallest charge: 3 credits. A free account starts with 20 credits and is topped up to 3 each day. A request that takes several steps costs more than the smallest charge. [Typical ranges are on the pricing page](https://qelvra.in/pricing).

Ask it like this:
- [Optimise a page on my site for its target keyword](https://qelvra.in/app?ask=Optimise%20a%20page%20on%20%7Bsite%7D%20for%20its%20target%20keyword)
- [Build an on-page plan for a keyword on my site](https://qelvra.in/app?ask=Build%20an%20on-page%20plan%20for%20a%20keyword%20on%20%7Bsite%7D)

## What this playbook does

On-page optimisation turns one existing page into a page built for one search. You name the page, and the agent hands back the exact changes: a new title tag, a meta description, the H1, a revised outline with the subtopics the page is missing, and the internal links and schema to add.

Reach for it when a page is close but not winning: it sits on page two of Google, or it gets impressions and few clicks. It suits an owner or marketer who wants a list of edits for one page, not a full-site audit.

## How the agent works through it

1. Reads the live page: its tags, headings, schema, word count and main text. Content that appears only after JavaScript runs is not seen.
2. With Search Console connected, pulls the searches the page has appeared for over the last 90 days, most impressions first, with clicks, impressions and average position.
3. Picks the primary keyword: the search with the most impressions where the page sits between positions 4 and 20, unless you name the keyword yourself.
4. Builds a brief from the current Google top 10 for that keyword (mobile results, India unless you ask for another market). It reads each competing page's title, headings and word count, collects the subtopics several of them share and the People Also Ask questions, and, where it compares your page, lists which of those subtopics it lacks.
5. Searches your sitemap for related pages on your own site that could link to this one.
6. Writes the plan: a title of 60 characters or fewer, a meta description of 155 or fewer, one H1, the revised outline, terms and entities to work in, internal links to add, and the schema types the ranking pages use.

## What you get back

One plan for the page, in the chat, built from your page as it is now, the competing pages and, when connected, your Search Console searches. The title and description fit the limits above, ready to paste into your CMS.

An example of the shape of the answer, for a made-up site (not real data):

| Element | Now | Suggested |
|---|---|---|
| Title | Bedsheets – Rangrez Prints | Hand Block Print Bedsheets, Jaipur Cotton – Rangrez |
| H1 | Our Bedsheets | Hand Block Print Bedsheets from Jaipur |
| Missing subtopics | none listed | How to wash block print cotton; King vs queen sizes |
| Links to add | – | From /blog/sanganeri-vs-bagru-prints, anchor "Sanganeri block print bedsheets" |

## What it needs

- The site added to Qelvra, and the page you want to work on (a full URL or a path like `/bedsheets`).
- Search Console is optional but changes the answer. With it, the agent chooses the keyword from the searches your page already ranks for. Without it, tell the agent the keyword you want the page to rank for; the rest of the plan works the same.
- A sitemap on your site, so the agent can find pages to link from. Without one, the internal-link part of the plan is thin.

## Where it stops

- It plans the edit; it does not make it as part of this playbook. If WordPress (posts and pages) or Shopify (blog articles only) is connected you can ask the agent to change the SEO title and description, and any change to a live page waits for your approval.
- It works on one page per run and needs a keyword to aim at. If you only want a quick score of a page's tags with no plan, the free [on-page SEO checker](https://qelvra.in/tools/on-page-seo-checker) does that without signing in.
- The benchmark is the top 10 at the moment of the run. Competitor pages that refuse the request are left out of the comparison and listed as not fetched.
- Search volumes in the brief are estimates from a third-party data provider, not Google's own counts.

## Frequently asked questions

### Can I choose the keyword myself?

Yes. Name it in your message and the agent uses it instead of picking one from Search Console. Do this when the page is new and has no search data yet.

### Why does it prefer keywords in positions 4 to 20?

Google already shows a page in that range for the search, so on-page work is the cheapest thing to try first. A page further down may need more than new headings, such as a fuller rewrite or links.

### Will it rewrite my whole page?

No. You get the title, description, H1 and a revised outline with what to add. If you want the full new text, ask for it next and the agent can write it as a document; [the content writing playbook](https://qelvra.in/playbooks/seo-content-writing) covers that job.

### Does changing the title risk the rankings I have?

It can, if the new title drops words the page already ranks for. With Search Console connected you can ask the agent to list those searches and check the new title against them. Change one page, wait a few weeks, and compare its clicks before you do the next.
