Import top pages from Google Search Console

Add high-click same-host URLs to Monitored Pages.

Last checked 20 August 2026

Use Import from GSC to seed Monitored Pages with URLs that already receive Google Search clicks. It is a one-time import action, not an ongoing synchronization.

This later import adds pages immediately. It is separate from first-run Sources, which can detect the same top pages as suggestions after you connect Search Console. On Sources, you still choose Add selected or Add all.

Import pages

  1. Open Websites and select the connected website.
  2. Scroll to Monitored Pages.
  3. Select Import from GSC.
  4. In Import from Google Search Console, choose 10, 25, 50, or 100, or enter a value in How many top pages.
  5. The allowed range is 1 to 250. Values outside that range are adjusted automatically.
  6. Select Import pages.
  7. Wait for the confirmation message before closing the dialog.

TechDash reports either the number imported and skipped, No new pages to import. Those URLs are already monitored or are on another host., or Search Console did not return any pages for that range.

What TechDash requests

The query asks the connected Search Console property for page rows:

  • From the previous 28 date values, ending yesterday
  • For Google's web search type
  • Grouped by page
  • Limited to the number you selected

Search Analytics results are ordered by clicks, so this is a practical list of high-click pages rather than a complete property export. Google states that the API returns top rows and does not guarantee every available row.

TechDash caches an identical interactive top-page request for one minute. Repeating the same import immediately may reuse that result instead of making another Google request.

Which results are added

For each URL returned by Google, TechDash:

  1. Parses the URL.
  2. Accepts the website hostname or its equivalent with or without a leading www..
  3. Keeps the path and query string.
  4. Converts it to a monitored path on the TechDash website's stored origin.
  5. Attempts to create the page with normal monitored-page defaults.

URLs from another hostname are skipped. A different protocol does not create a separate monitored origin because TechDash imports the path onto the website already stored in TechDash.

A URL is also skipped when it cannot be parsed or when creating that monitored path fails, including because it already exists. Imported pages use the standard default page settings: the website's normal check interval, monitoring enabled, default notification choices, and the default set of checks.

Review the import

After the confirmation:

  1. Use Filter pages in Monitored Pages to locate an imported path.
  2. Select the path to review Interval, Enabled, Notify, and Optional checks.
  3. Remove low-value pages or change their schedule if needed.
  4. Run another import with a larger limit only if the first set was useful.

Choose pages that represent important templates, conversions, or organic landing pages. Importing the maximum is not automatically better. Every enabled page adds scheduled crawl work, and URL Inspection has a separate daily safety budget.

If no pages are imported

Search Console did not return any pages for that range. means the API returned no page rows. Possible reasons include a new or low-traffic property, a reporting delay, the wrong matched property, or no web-search clicks in the requested range.

No new pages to import. Those URLs are already monitored or are on another host. means Search Console did return rows, but TechDash skipped all of them. Check the existing list and confirm the property represents the hostname you intended.

An error toast instead of either message can indicate expired Google authorization, lost property permission, a Google rate limit, a temporary service problem, or a network timeout. Keep the exact text. Do not repeatedly submit the same import to work around quota.

Sources

Related articles