Suggest page titles that state the topic and useful distinction clearly. Match the title to the page instead of adding extra keywords.
How to use
Sign in and supply the content or a precise summary. Add the main query and audience in context. Choose a title that reflects the actual answer.
Example
For a page on freezing basil, prefer a specific title about preparation and storage to a broad promise about all herbs.
FAQ
Is there an exact title length for Google?
Display depends on context and device. Keep titles concise and descriptive; Google can generate a different title link.
Related tools
A practical task
Choose the central promise only after reading the page. A converter title should name both formats; a guide title should state the question it answers. Keep the brand short so it does not bury the part that distinguishes this page from another.
Another useful question
Should I add every keyword variation?
No. Close variants make a title repetitive. Use the natural name of the task and one meaningful distinction that the page actually supports.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Metadata and page content | A title and description should summarize the page a visitor will actually find. Search engines can choose other wording for a query. Clear, distinct summaries are more useful than repeating a keyword in every available field. |
| Canonical signals | A canonical tag indicates a preferred URL among duplicate or similar pages. It is a signal rather than a command. Internal links, redirects, sitemaps, and actual content should agree about the preferred address. |
| URL components | A URL contains structure such as scheme, host, path, query, and fragment. Characters that separate those parts differ from characters inside a value. Encode the right component rather than transforming the full address blindly. |
| Query values | Query separators connect parameter names and values. An ampersand inside a value must not be confused with the separator between parameters. Build the URL with correct component encoding before sharing it. |
| URL fragments | A fragment points to a location within a resource and is normally not sent as part of the server request. It differs from a query parameter. Changing it does not necessarily create a different document for canonical selection. |
| Structured data | Structured data describes entities and facts in a machine readable format. It must match visible page content. A valid JSON document is not proof of eligibility for a search feature or a promise of richer display. |
| Source boundaries | A summary or rewrite works from the material you provide. A URL alone does not supply the full article in this interface. Include the relevant passage and keep citations attached to the claims they support. |