Search visibility: your website inside the ERP

Search visibility brings the content map of your company’s websites into the ERP: all their pages, what each one says and which Google search it targets. The ERP reads your website —your WordPress or its sitemap— and, if you connect it, what Google does with it (Search Console and Analytics); you decide the plan: which page owns each query. It is in Marketing → Search visibility.
What is it for?
A company website grows in parts: sales pages, blog posts, guides, a glossary. Each part is written by someone different, and after a year there are two or three pages targeting the same query without anyone having decided it. Google doesn’t know which one to show and they all do worse.
Search visibility puts things in order with a list of owners: each query, one page (or a planned piece that isn’t on the website yet, or an article of yours on another website). The screen has ten tabs:
- Map: all the pages of the website, with what the website says about each one and what you decide (its scope, its cluster, its target query and its intent). On each page’s record, the pre-publication review, its place on the publishing board and its performance on Google.
- Conflicts: the pairs of your pages that overlap, with the evidence and what you decide to do with each one, and the pieces in the editorial plan that already conflict before they are written.
- Clusters: the topics of your website, each with its pillar page and its queries, and the clusters the ERP proposes to you from the queries of a topic, for you to accept, change or reject.
- Keywords: the Google queries for each topic of what you sell, with their volume, their trend, their difficulty, the page of yours that already owns them and the SEO score; the action that proposes new queries for a topic; and the cross-checks with the Google Ads ads.
- Editorial plan: the pieces you are going to publish that aren’t on the website yet, with their cluster, their query, who is in charge of them, who writes them, when they are due, whether they conflict with what is published or planned, and their brief.
- Calendar: the pieces in a month or a week by their date, with what was published on those days, the warnings about a poor spread, the gaps in the marketing goals and the suggested date of each piece; you move them by dragging them or with the keyboard.
- Guests: the articles a guest writes on your website and yours on other websites, with the query they target and whether their link to your website is still there.
- Maintenance: published content that needs work —pages losing visits, queries with a low CTR for their position, pieces that aren’t ranking after 90 days, definitions without a glossary entry and missing internal links—, to accept or dismiss.
- Guidelines: what marketing tells the query plan (priorities, vetoes, goals, channel and notes for the AI), which overrides everything here and in Google Ads, and the SEO weights and thresholds. The guidelines can also be opened from Marketing → Search opportunities, with the permission of either of the two.
- Sites: your websites, where they are read from, their connection with Google and the synchronisation that keeps the map up to date.
Where does the ERP read my website from?
From one or more sources. Each site (your website) can have as many as it needs:
- WordPress: through the WordPress API, the ERP reads the blog posts, the pages, your website’s own content types (products, guides, glossary…) and their categories. With an Editor user’s application password it also reads drafts, content pending review, scheduled content and private content.
- Sitemap: the index of pages that any website publishes, with or without WordPress. It is useful for a website made with another tool or for a section that is kept separate, such as a help manual.
The ERP only reads. It changes nothing on your website.
Where do I start?
- Add your website and test the connection: create the site, add the WordPress source or the sitemap to it, give it the application password and check with Test connection that the ERP sees what it should see.
- Sync your website: the ERP reads it and fills the map. The first time, a large website takes several synchronisations.
- Decide what each page targets: on the map, the scope, the cluster, the target query and the intent of each page.
- Let the assistant propose it: it proposes the target query, the intent, the scope and the cluster of the pages that don’t have them, and you accept or dismiss them in bulk. Each proposal costs 2 AI credits.
- Deal with the conflicts: the pages that overlap, and what to do with each pair (differentiate them, merge them, de-optimise one or take it out of the index).
- Review before publishing: the ERP reads the page at that moment and runs ten rules on it; a traffic light says whether it is ready and each finding, what to fix.
- Manage publications on a board: each page (or planned piece) is a task that goes from idea to measurement, and the example schedules review it when it enters Revisión SEO, sync the website every night, warn about new conflicts, measure each page a month after it is published, request intent proposals every week, check the editorial plan conflicts every night and, every week, the links of the guest posts and the maintenance of published content. The Refrescar column collects published content that needs updating.
- Connect your website with Google: with a service account, the ERP reads from Search Console and Analytics the impressions, clicks, position and conversions of each page, and the queries that two of your pages share.
- Set up the Looker Studio dashboard: the ERP writes the map to a Google sheet, and Looker Studio joins it with Search Console and Analytics to show performance by cluster and by scope, cannibalisation, opportunities and how recent publications are doing.
How does marketing plan what is going to be published?
With the website already on the map, marketing decides what to write and when, using the same query bank as the Google Ads campaigns. The steps, in the order they are done:
- Set the marketing guidelines: what goes up, what isn’t talked about, how many pieces a month and through which channel each query is worked. They override the ERP’s proposals, here and in the Google Ads campaigns, and after each change you see what has changed in the scores.
- Find the keywords for a topic: it brings together what Search Console already sees, the ideas from the real search data, the Keyword Planner file you upload and the AI candidates, and ranks them by their SEO score, with the coefficients in view. From each row you change the intent or the topic, veto it or set the channel.
- Group the queries into clusters: the ERP proposes the clusters of a topic —a pillar query and its child queries— with what Google shows, Search Console and the meaning; the AI only names them. You accept them, rename them, move queries, merge them, split them or lock them; nothing is created without your accepting it.
- Plan the pieces: each piece you are going to publish already owns its queries, with its owner, its author and its date; create the missing ones in a cluster in one go, merge them or discard them, and send them to the publishing board. When its page appears on the website, the synchronisation links it by itself.
- Spread the pieces across the calendar: each piece on its day, with warnings if two from the same cluster are too close together, if a week fills up or if the intent is repeated in a cluster (any warning can be skipped with its reason); the gaps in the marketing goals with Create a piece here; and the suggested date based on the search peak, also for all the undated ideas at once.
- Check the conflicts before writing: each piece is compared with what is published, with what is planned and with your articles on other websites, and the ERP tells you what is best to do: create it, improve the page you already have, merge them or differentiate it.
- Manage guest posts: a guest’s post on your website goes into the editorial plan and isn’t accepted if it conflicts or the calendar warns without a reason; yours on another website warns you if it targets a query that already belongs to a page of yours, and its link is checked every week (an anti-bot doesn’t count it as lost).
- Cross-check SEO with ads: lower the bid on what already ranks at the top without paying, write about what converts in the ads, an article instead of an expensive ad, and ads for the piece that isn’t ranking yet. They are proposals with their reason; the marketing channel guideline always wins.
- Maintain published content: refresh what is losing visits, rewrite the title and meta description of what ranks well but doesn’t get clicked, refresh the pieces that aren’t ranking after 90 days and write the missing glossary entries. The 30-day and 90-day measurement of each piece stays in the editorial plan.
- Prepare the brief for each piece: the AI proposes the SEO title, the H1, the meta description, the sections, the questions, the internal links and what it shouldn’t cover, with your website’s data and without making up figures. You change it as you like and copy it for whoever writes it. Each brief costs 60 AI credits. And complete the internal linking: the pages that don’t link to their pillar, the similar sibling pages that don’t link to each other and the pages no other page links to, with where to put each link and with what text.
- Turn on real search data when you want real figures: the volume of each query with a year of history, its difficulty, Google’s top ten and what it costs to appear in the ads (they cost credits, you are told beforehand, only what enters the bank is charged, and they are turned on per website with Automatic query). Without them everything works with Search Console and the Keyword Planner file you upload, which brings, free, the searches for each month and the ad competition. At each step that needs them, a panel warns you what each query costs and lets you turn off the ones you don’t want: query real search data: what it costs.
What can marketing change?
Everything the ERP proposes is a proposal: marketing accepts it, changes it or rejects it, and the plan is recalculated with what it says. This is what can be changed, and where:
| What | Where |
|---|---|
| The clusters: accept or reject them, rename them, change their pillar, move queries from one to another, merge them, split them and lock them | Clusters |
| The pieces: add them, remove them, merge them, discard them, change their title, their type, their main query and the secondary ones, their owner and their author | Editorial plan |
| The dates: set them, drag them to another day and accept or adjust the suggested dates | Calendar |
| The queries: their intent and their topic, add one by hand or remove it from the topic | Keywords |
| The priorities: raise or lower a topic, a cluster, a query or the queries with a term | Guidelines |
| The vetoes: what isn’t talked about, neither on the website nor in the ads | Guidelines, or Veto on the query’s row |
| The channel: SEO only, ads only or both, by topic or by query | Guidelines, or Channel on the query’s row |
| The goals: how many pieces a month for a cluster, a topic or everything | Guidelines |
| The notes for the AI: what the AI has to bear in mind when proposing queries, naming clusters and preparing briefs | Guidelines |
| The weights and thresholds: how much each factor of the SEO score counts, when two queries go into the same cluster, when two pieces conflict, the calendar rules, the cross-checks with the ads, maintenance and linking | Guidelines |
| The conflicts and warnings: accept a piece’s conflict with its reason, skip a calendar warning with its reason and accept a guest post that conflicts, also with its reason | Conflicts, Calendar and Guests |
| The cross-check and maintenance proposals: accept or dismiss them | Cross-checks and Maintenance |
| A piece’s brief: change it by hand | A piece’s brief |
What is done by hand isn’t overwritten by anyone. No rule, no AI and no website synchronisation changes an intent, a topic, a query, a cluster or a piece that a person decided. What was rejected isn’t proposed again unless the data that led to it change. An accepted conflict or warning doesn’t warn again unless what caused it changes.
Each change recalculates what depends on it: the scores, the conflicts and the calendar gaps. Above the tab you see what has changed (‘3 queries go up, 1 drops out by veto’).
What should I know beforehand?
- To read drafts you need a WordPress Editor user. Without a credential, the ERP sees the same as any visitor: what is published.
- An Editor can’t see unpublished WooCommerce products. For products, what is published is read.
- If your website is in several languages, each language other than the main one is marked with its address prefix (for example,
/en/for English). The main language goes at the root, without a prefix. The versions of the same page in several languages recognise each other and aren’t counted as pages that overlap. - Reading a large website takes time. The ERP requests the pages a few at a time and with pauses, so as not to load your server, and spreads the reading across several synchronisations.
- What you decide isn’t lost. Reading the website again never changes the scope set by hand, the cluster, the target query, the intent or the notes of a page.
- If your website has an anti-bot that doesn’t let the ERP through (it gives it its waiting page instead of yours), the ERP recognises it, doesn’t save that page and tells you how to let it in.
More about Search positioning
- Guest posts
- Proposed clusters
- Connect your website with Google: Search Console and Analytics
- Query real search data: what it costs
- Cross-checks between SEO and ads
- Add your website and test the connection
- Search data: volume, difficulty and Google results
- Marketing guidelines: what marketing tells the plan
- The editorial calendar
- A piece’s brief
- The content map: what each page of your website targets
- The Looker Studio dashboard: your content map alongside what Google measures