Start on-page SEO with the question the page answers
On-page SEO work begins by describing the reader’s task. Someone seeking a definition, choosing a product or evaluating a service may need different pages. Consider existing queries, customer questions and current result types together. Search volume is an input, not proof of a suitable customer. Long-tail queries are not automatically easier to rank for or more likely to convert. Research the actual decision before selecting the format.
Define the promise, scope, sources and next step in the brief. On-page changes happen on your own page; off-page work depends on other publications and people. There is no universal equal-budget rule or ranking guarantee. Explain genuine experience, methods and review ownership. Adding a biography alone does not establish expertise. Health, legal and financial subjects require appropriate specialist assessment. Publishing on the Prix website does not automatically satisfy every requirement of a sensitive subject or imply a professional review has occurred.
Align titles, descriptions and URLs with the actual promise
A content plan should give each page an accurate, distinct title. Google’s title guidance recommends concise, descriptive text; the displayed search title can use different sources. Avoid unnecessary repetition and long identical branding across all pages. Character and pixel previews can support design checks, but are not fixed ranking requirements. Make the important difference understandable before adding marketing language.
The Google snippet guide explains that descriptions may be used and results can be shortened to fit device width. Write a truthful summary without misleading calls to action. Do not promise the cheapest option or a guarantee the business cannot deliver. Keep URLs readable and maintainable. Avoid changing an established working address simply to insert a keyword. When a change is needed, plan old links, redirects, canonicals and sitemap updates together so the published destination remains coherent.
Title check
Does it explain the subject and difference without repetition or false promises?
Description check
Does it summarise the real scope without inventing delivery or outcomes?
URL check
Does it support a stable task, with appropriate mapping if changed?
FROM READING TO A NEXT STEP
Improve the content and technical task of your priority page
Share the page, audience and current problem. We can build an implementation plan from research through launch acceptance.
Organise headings and links around the reader’s decision
Page architecture needs a clear main heading and meaningful sections. One H1 can be a sensible editorial standard; additional H1s alone do not prove a penalty. Use H2s for major questions and H3s for necessary subdivisions. Do not repeat the same phrase in every heading. Opening paragraphs should explain the section’s answer or purpose. Lists, tables and a contents menu should help people scan actual information rather than decorate empty material.
Google’s link guidance discusses accessible href links and descriptive anchors. Add contextual internal links where they answer the next question. Do not insert unrelated city and service phrases repeatedly. Check orphan pages, broken targets and unnecessary redirect chains. External sources should support the specific claim; increasing link count is not independent evidence of quality. Qualify appropriate advertising, user-generated and other relationships separately, with actual rendered destinations verified after publication.
Test images, mobile layout and CTAs against real tasks
Page experience review goes beyond text and scores. Ask what an actual image, diagram or example helps a reader understand. Clarify permission, source and what the visual represents. A design project should not become a result for another service. Select dimensions and suitable formats without losing legibility. Explicit sizes can reduce shifts; assess loading rather than blindly lazy-load the first important image. Media should divide and explain the content, not delay its essential answer.
Alternative text should describe the image in context rather than list keywords. Avoid unnecessary descriptions for purely decorative media. Check mobile tables, menus, cards, forms, keyboard access and error messages. The CTA should name a suitable action for this decision stage. Form opening, server acceptance and a qualified request are different behaviours. Long reading time is not always success; a quickly answered question may be a good experience. Do not turn GA4 engagement into a direct Google ranking coefficient or claim a decorative animation creates qualified demand.
Verify crawling, noindex, canonicals and performance separately
Technical SEO checks begin with status codes, robots, meta robots, canonicals and sitemap consistency. Robots.txt controls crawling; it does not independently prevent indexing or secure private information. The Google noindex guide explains that a page must be crawlable for the signal to be seen. Private material needs actual access controls. A canonical indicates a preference among duplicates; assigning every filter to one address is not a universal fix or guaranteed penalty removal.
Review HTTPS, redirects and essential content on mobile. Current Core Web Vitals cover LCP, INP and CLS; FID is no longer a core metric. Interpret good thresholds with appropriate field percentiles and device context. A laboratory score is different from actual visitor data. Do not apply caching, CDN or CSS and JavaScript changes indiscriminately; investigate the bottleneck and test important tasks. Good performance cannot guarantee a particular position or prove the whole system is error-free.
Match structured data and AI claims with visible facts
Structured data implementation should use suitable types and properties for visible information. Product, organisation, article and breadcrumb data must describe the actual page. Do not invent prices, ratings, expert approval or delivery times. Technical validation can assess eligibility, but cannot guarantee enhanced presentation. Google’s 2026 update record documents the end of FAQ rich results. Visible FAQs can remain useful for people without that search feature.
Google’s AI features guidance says fundamental SEO remains relevant for AI Overviews and AI Mode, with no special additional file or markup requirement. That is Google-specific, not proof every answer engine follows identical rules. Clear answers, sources, dates and genuine evidence help readers, but fixed paragraph lengths cannot guarantee citations. GEO does not mean ordinary SEO has disappeared. When AI assists production, a human should check accuracy, actual experience and update ownership rather than publish unsupported statistics or credentials.
Complete launch checks with an owner and evidence
A launch checklist helps teams assess the same deliverable. Record a representative URL, issue, owner and acceptance test for each finding. Elements that appear correct in a preview may differ in live HTML; verify the actual release and mobile flow. Do not add unavailable pages to the sitemap. Update dates with meaningful revisions and genuine review rather than fabricate historical publication dates. Keep the release record understandable for future maintenance.
The cards illustrate acceptance checks, not guaranteed indexing or rankings. If several changes happen together, explain the limits of attributing subsequent outcomes. Fix priority tasks before creating more pages to compensate. Repeat maintenance when sources, links or product information change. Exclude access keys and private customer data from reports. Content, development and business owners should close the review together so recommendations become verified implementation.
Task
Do the search need, scope and supported answer match?
Identity
Are the title, description, main heading and actual dates coherent?
Links
Are destinations correct and important pages discoverable?
Media
Are images permitted, accurately labelled and legible?
Access
Do status, robots, noindex, canonical and sitemap agree?
Mobile task
Do reading, navigation and contact genuinely work?
Data and markup
Do visible facts match markup and required acceptance events?
Maintenance
Are issues, owners, changes and follow-up checks recorded?
Interpret tools through implementation and actual outcomes
Choose SEO scope by separating research, actual fixes, content review and monitoring. Search Console provides query, visibility and indexing context. PageSpeed Insights and GTmetrix reflect particular testing conditions. Screaming Frog, Ahrefs and Semrush offer different crawling and research coverage. Having a tool does not mean the recommendation has been implemented. Inspect the current page rather than rely on an obsolete report name or a green plugin indicator.
GA4 events describe behaviour within the configured and consented measurement scope. Verify form success and suitable requests separately against operational records. Report rankings, clicks and costs with period, sample, seasonality and release changes. Avoid fixed few-week or three-to-six-month outcomes and permanent-gain promises. Share the website, priority page, problem and implementation capacity in the first brief. Begin with a practical list of verified issues instead of uncertain metric targets. Reassess the same tasks after implementation before expanding the programme.
BEFORE YOU DECIDE
Frequently asked questions
Are on-page and technical SEO identical?
They overlap. This guide connects content and interface tasks with technical access; site-wide infrastructure can require separate assessment.
Are there mandatory title and description character counts?
Google does not specify fixed counts as ranking requirements. Write concise, accurate text; results may be shortened for device width.
What keyword-density percentage should we use?
Do not impose a universal percentage. Natural language, actual subjects and reader tasks matter; LSI lists or repetition counts do not prove quality.
Can robots.txt hide private pages?
No. Crawl controls are not access security. Private content needs authorisation; indexing controls such as noindex are considered separately.
Will special FAQ or AI markup guarantee visibility?
No. FAQ rich results ended, and Google AI features do not require special additional files or schema.
How soon will rankings improve after checks pass?
Checks are not a ranking timetable. Crawling, indexing and serving are not guaranteed; monitor actual periods and changes.
LET’S DEFINE THE SCOPE
Improve the content and technical task of your priority page
Share the page, audience and current problem. We can build an implementation plan from research through launch acceptance.
Discuss on-page SEO scope