Expand a ranking page with the queries it already gets but does not cover
A query-by-query coverage table for one URL plus draft sections for the biggest gaps, ready to approve.
When to use it
When a page already ranks and gets impressions, but you want it to capture more of the related queries it only partly answers.
What you get
A query-by-query coverage table for one URL plus draft H2 sections for the 5 biggest gaps with insertion points, with the WordPress post updated only after you approve.
Does it change anything in my account?
Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.
Works with
Search Console, WordPress
Fill in before sending
[property][URL]
Use my Opus Growth connection for this. If you cannot see the tool you need, search among the Opus Growth tools (with search_tools if it is in your list); if you cannot reach the tools at all, do not guess, tell me.
Work on the Search Console property [property] and the page [URL] on the client's WordPress site.
1. Pull the last 90 days of Search Console data for this page by query. Keep queries with at least 100 impressions and an average position between 5 and 20.
2. Read the full page content from WordPress and check whether each query, or a close variant, is answered in the headings or body.
3. Deliver a table with these columns: query, impressions, clicks, CTR, average position, coverage (yes / partial / no), and recommended action. The action must be one of: new H2 section, expand existing section, add FAQ item, or ignore as off-topic.
4. Draft new content for the 5 uncovered or partially covered queries with the most impressions. Write an H2 and 80 to 150 words for each, in the page's existing tone. Use concrete facts only and no filler.
5. Show where each block would be inserted in the current page.
Do not edit the page yet. Present the updated content as a preview and wait for my explicit approval before updating the post.
Adds an English version of a static site under /en/: per-language URLs, hreflang and x-default, og:locale and schema language per language, a static language switcher, per-language sitemaps and llms.txt. Checks translation pairing and quality with a script and measures every page on two devices.
When to use itWhen you want to add an English version to your Turkish site hosted on Opus Growth and have each language show up in the right place in search without competing with the other.
Pulls the questions the page already gets in Search Console and who AI answers cite, then reorganises the existing content with a direct answer up top, question headings, a comparison table and a page-specific FAQ. Invents nothing, applies after preview and approval, and records a baseline for measurement.
When to use itYour service or product page ranks in Google but is not quoted in AI answers, or its most important information is buried under a long introduction.
Checks hreflang, canonical and html lang alignment on every language version, the alternates in the sitemap and any automatic redirects based on the visitor's country or browser language. Measures which version Google picks and which language page AI answers cite, without changing anything.
When to use itYour site is published in several languages and one language version does not show up in its own market in Google or AI answers, while a page in another language appears instead.