Skip to content

Search visibility: your website inside the ERP

Brass compass on a folded paper map on a wooden table

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:

Where does the ERP read my website from?

From one or more sources. Each site (your website) can have as many as it needs:

The ERP only reads. It changes nothing on your website.

Where do I start?

  1. 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.
  2. Sync your website: the ERP reads it and fills the map. The first time, a large website takes several synchronisations.
  3. Decide what each page targets: on the map, the scope, the cluster, the target query and the intent of each page.
  4. 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.
  5. 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).
  6. 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.
  7. 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.
  8. 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.
  9. 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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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).
  8. 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.
  9. 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.
  10. 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.
  11. 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:

WhatWhere
The clusters: accept or reject them, rename them, change their pillar, move queries from one to another, merge them, split them and lock themClusters
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 authorEditorial plan
The dates: set them, drag them to another day and accept or adjust the suggested datesCalendar
The queries: their intent and their topic, add one by hand or remove it from the topicKeywords
The priorities: raise or lower a topic, a cluster, a query or the queries with a termGuidelines
The vetoes: what isn’t talked about, neither on the website nor in the adsGuidelines, or Veto on the query’s row
The channel: SEO only, ads only or both, by topic or by queryGuidelines, or Channel on the query’s row
The goals: how many pieces a month for a cluster, a topic or everythingGuidelines
The notes for the AI: what the AI has to bear in mind when proposing queries, naming clusters and preparing briefsGuidelines
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 linkingGuidelines
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 reasonConflicts, Calendar and Guests
The cross-check and maintenance proposals: accept or dismiss themCross-checks and Maintenance
A piece’s brief: change it by handA 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?

More about Search positioning