Sync your website with the content map
Syncing means the ERP reads your website and brings the content map up to date: it adds new pages, updates what changed and marks as withdrawn what is no longer there. It never touches what you have decided (the scope set by hand, the cluster, the target query, the intent and the notes). You do it in Marketing → Search visibility, Sites tab, with Sync now.
How do I sync my website?
- In the Sites tab, open your website. It must have at least one source (WordPress or sitemap) and be Active.
- Under Synchronisation, click Sync now.
- When it finishes, the summary appears below: what was read from each source, how many pages are new, changed and withdrawn, and how many are still to be read.
You need the Changes permission on Search visibility.
The synchronisation can also be scheduled (for example, every night) from Tasks → Schedules, with the sincronizar_sitio_web tool, or you can ask the assistant for it: ‘sync the website’. It is the same synchronisation in all three cases.
What does it read from my website in each synchronisation?
Two things, in this order:
- The list of pages from each source: what there is, in what status (published, draft, scheduled…), its title, its categories and when it changed. In WordPress, the blog and store categories are also included, because each one is a page that Google sees.
- Each published page, as Google sees it: the title the search engine shows, the meta description, the robots, the canonical, the H1, the versions in other languages and which pages of your website it links to (what the internal linking looks at). Only the page that is new, the one that changed since last time or the one that hasn’t been looked at for some days is read.
And, if the website is connected with Google, at the same time what Google says about each page (impressions, clicks, position, queries, visits and conversions), in complete weeks. The summary has its Google line; when there is no new week to request, it says Up to date.
If you have the CRM, the synchronisation also updates the query bank, the same one the Google Ads campaigns use (Marketing → Search opportunities): the queries Google shows your website for go into it once a week, and each page’s target query is recorded as the query that page owns. If two pages have the same target query, only one is the owner; the other keeps appearing in Conflicts. What you have decided in the bank (a query’s intent, who you gave it to) isn’t touched. The summary has its Query bank line.
If the bank doesn’t respond, the line shows in red and those queries are carried over to the next synchronisation, without waiting for the following week. And if a query that had an owner is no longer in the bank (because it was emptied from Opportunities), the synchronisation removes that assignment and counts it on the same line; the page owns its target query again.
If you have pieces in the editorial plan, the synchronisation also looks for their page: the one that appears on the website with the WordPress ID or the address you put on the piece is linked to it (the page becomes the owner of its queries), and the one that only resembles it by title is proposed to you so that you can confirm it. The summary has its Editorial plan line when there are pieces waiting for their page.
Finally, if your website has a sheet for Looker Studio, the ERP rewrites it with the map at that moment: one row per page. The summary has its Sheet line, with the rows written. It is explained in the Looker Studio dashboard.
The ERP only reads your website: it changes nothing on it, nor in Search Console or Analytics. The only thing it writes is that sheet.
Why isn’t the whole website read at once?
Because a large website takes time. Reading the published page of each post is one request per page, and the ERP requests them a few at a time and with pauses so as not to load your server. A website with five hundred pages takes several minutes.
That is why each synchronisation works for a while and stops: it saves what it has read and leaves the rest for the next one. The summary says so: 420 left for the next syncs. Each page knows whether it is still waiting to be read, so the next one carries on where it left off.
The first time, click Sync now several times in a row until there are none left, or let the schedule do it. After that, each synchronisation reads only what has changed and finishes straight away.
How often is the whole list read?
Each synchronisation requests only what has changed since the previous one. Once a week it requests the whole list: it is the only way to know that a page is no longer there.
If you click Sync now shortly after another synchronisation, the list isn’t requested again: the time goes to the pending pages. The summary says so: List read 5 minutes ago.
What happens to a page that is no longer on the website?
It changes to Withdrawn on the map, with its decisions and its history. This only happens when the ERP has read the whole list for that content type and the page wasn’t there. If a type couldn’t be read (because of a website error or because the credential doesn’t reach it), its pages stay as they were: the ERP doesn’t assume that what it couldn’t see has disappeared.
If a page changes address in WordPress, the ERP recognises it by its number and moves it with everything that had been decided.
What are scope rules and how do I change them?
Scope rules decide the scope of each page you haven’t set by hand. They are on the site’s record, in Scope rules. Each rule states a condition and the scope it proposes:
- The content type is
post→ Blog. - The path starts with
/ayuda/→ Help. - Is in the category
Factura electrónica→ Function.
They are tried from top to bottom and the first one that matches wins; whatever doesn’t match any is Other. With the arrows you change the order. Each change is applied straight away to the pages on the map, without waiting for the next synchronisation.
A website’s first synchronisation creates the usual rules for the types it has: posts → Blog, pages → Sales, products → Product, glossary → Glossary, guides → Help and categories → Category. The listings of the website’s other custom taxonomies (for example, the letters of a glossary) also go to Category. A sitemap that lives in a folder (/ayuda/sitemap.xml) adds its own: whatever starts with /ayuda/ is Help. If you delete them, or if the website introduces new content types or taxonomies, Built-in rules proposes the missing ones.
Changing the rules requires the Create permission: they are the site’s settings.
Does the ERP tell me when I publish a page?
Yes. When a synchronisation finds a newly published page —a new one, or a draft that has changed to published—, the ERP records the event A page on the company website has been published. With it you can schedule things in Tasks → Schedules, such as reviewing that page or measuring how it is doing after a month. You are notified once per page.
On a website’s first synchronisation nothing is notified: what was already published hasn’t just been published.
What do I do if the summary says something has failed?
| What you see | Why | What to do |
|---|---|---|
| ‘There is no time left for its list in this run’ | The other source has used up the time | Nothing: it is read first in the next synchronisation |
| ‘List read N minutes ago’ | It has just been read | Nothing: this time the time goes to the pending pages |
| ‘The list did not finish within one run’s time’ | The website takes a long time to reply | If it always happens, ask support to increase the time per synchronisation |
| ‘…couldn’t be read: the website isn’t responding’ | Your website isn’t replying at that moment | Sync again later |
| ‘N could not be read’ in the pages | Those pages give an error (for example, they don’t exist) | Open them in the browser: if they give an error, fix them on your website |
| ‘The website responded… with the Imunify360 waiting page’ (or Cloudflare’s, Sucuri’s…) in red | An anti-bot on your website distrusts the ERP and gives it its waiting page instead of yours. The ERP doesn’t save that page, leaves yours as they were and, if it happens several times in a row, stops requesting until the next synchronisation | Ask whoever looks after your website to add the ERP server’s IP or its identification (PowergestERP-Posicionamiento) to that protection’s allowlist. The pages will be read in the next synchronisation |
| ‘asks to be called more slowly (responds 429)’ | Your server limits requests | The same: the allowlist, or sync less often |
| ‘URLs from another domain have not been saved’ | Your sitemap links to pages on another website | Nothing: only those on your website go in |
| The Google line in red | Google doesn’t allow reading (the account has no access, the property is mistyped…) | Click Test connection on the Google card: it says what is failing and how to fix it. What failed is requested again in the next synchronisation |
| The Sheet line in red | The sheet couldn’t be written (it isn’t shared as Editor, it has been deleted, the ‘Mapa’ tab belongs to someone else…) | Click Test connection: the Sheet line says what is failing. The sheet stays as it was and is written in full in the next synchronisation |
| ‘There is no time left in this run to write the sheet’ | The website and Google have used up this synchronisation’s time | Nothing: it is written in the next one, or click Write the sheet now |
| The Query bank line in red | The CRM hasn’t responded | Nothing: the map and the Google data are saved. It is tried again in the next synchronisation |
| The Editorial plan line in red | The pieces couldn’t be linked to their pages | Nothing: the map is saved. It is tried again in the next synchronisation |
| A piece published on the website still isn’t linked | It has no planned address or WordPress ID, and its title isn’t similar enough | Put the address or the ID on its editorial plan record: it is linked in the next synchronisation |
| ‘N target queries already have another owner’ | Two pages target the same query, or you gave it to another page | Look at the Same target query conflict in Conflicts and decide which one keeps it |
Back to search visibility.
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