FAQ

ZipTie offers tons of useful features:

• A full list of unindexed URLs
• Get performance metrics, such as rendering time,
• Analyze how JavaScript changes content.
• Shortly we will integrate with Google Search Console to show you insights about traffic.

• – You can check the indexing of ANY website, including your competitors
• – You can monitor the sample over time and see which URLs got deindexed
• – Unlike in Google Search Console, you’re not limited to checking only 1000 URLs
• – You can get additional information about a given URL, structural (such as word count, title tags, structured data), performance (such as response time, page loading time), JavaScript dependence score, and more

The default user agent is the same as Chrome. However, you can specify a custom user agent while creating or editing a Project (this is useful when your server blocks ZipTie.dev).

Default desktop User-agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/X.X.X.X Safari/537.36
Where X is the current version of Chrome used by the ZipTie

Default mobile user-agent: 
Mozilla/5.0 (Linux; Android 10) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/X.X.X.X Mobile Safari/537.36
Where X is the current version of Chrome used by the ZipTie

Yes!

We present additional information about the URLs, such as:

• – Status code, indexability
• – Number of words (total number of words on a given page, excluding HTML markup and comments)
• – H1 tags, Title tags
• – Various performance metrics, including rendering time, CPU used 
• – Core Web Vitals metrics (Largest Contentful Paint, Cumulative Layout Shift)

Yes! If you need help with indexing issues or technical SEO overall, feel free to contact us!

You need to visit the Profile page and then click on Change Plan.

You can then select the plan that fits your needs best.

ZipTie will check which URLs in the sitemaps you provided, aren’t indexed in Google. By default, ZipTie will check all URLs in sitemaps. There is one exception though: if you limit the number of URLs, ZipTie will choose URLs randomly to fit into the limits.

Example: let’s assume there are 10k URLs in your sitemaps:

• • – if you set limit to 10k, ZipTie will check all URLs
  • – if you set limit to 1k, ZipTie will choose 1k randomly
  • – if you set limit to 100k, ZipTie will check all URLs and return 90k surplus credits

ZipTie will check which pages from your custom list of URLs aren’t indexed in Google.
Useful if you want to check very specific URLs. For instance, when you want to check a list of the most important products in your ecommerce store, or the latest news from your website. 

Your list should only contain URLs you want to check, separated with newlines, and without commas.
The list can be provided in two ways:

• • – Copy-paste your list
  • – Upload a TXT file

Before creating an audit ZipTie will try to check whether the URLs you have provided are eligible for checks.

ZipTie verifies the URL structure and whether the connection to the website is successful.

If you are certain that the URL is correct, it is possible that the website protection systems are effectively blocking ZipTie from accessing it. To solve this problem, you may need to add a certain User Agent to your domain whitelist, and pass it to ZipTie (in the Custom User Agent field in the Project advanced settings).

Contact us if the problem persists.

• ZipTie currently supports XML and RSS sitemaps only.
  If you have a TXT or HTML sitemap, extract the URLs and paste them into the URL list mode.
• Ensure that your sitemap is valid.  The easiest way to ensure your sitemap is valid is to check it’s validity via Google Search Console, or by checking the sitemap by an SEO crawler.

Before indexing check, ZipTie checks if a page is indexable (eligible for indexing). ZipTie will mark a page as not indexable if one of the following cases occurs:

• – A page is returning an HTTP status code other than 200
• – A page is canonicalized to another page
• – A page is blocked by robots.txt rules
• – A page has got a “noindex” in a meta tag or in a server’s HTTP header

• – With JavaScript Rendering enabled, our browsers execute JavaScript on every single page. It’s crucial for JavaScript-based websites
• – JavaScript Rendering mode is only available with Inspection Mode enabled
• – With this mode enabled, ZipTie renders pages the same way your browser does, so the audit can take longer

• – Monitoring lets you track the indexing of URLs in a given audit over time
• – You can easily detect if and when Google deindexed your URLs
• – Enabling monitoring for audit means ZipTie will perform automatic checks of it in the interval of your choice – for example, every 7 days
• – Credits will be used at the beginning of every check
• – Monitoring can be enabled or disabled at any moment
• – The number of possible monitored audits depends on your subscription plan.

• – In this field, you can specify how many times per second ZipTie will send requests to your website
• – Higher values mean faster checking and denser traffic on your site during the check. The default rate is 4 requests per second
• – When the server commonly returns 429 or 5xx HTTP status codes, try lowering the number of requests per second

– The limit depends on the plan you use. For Advanced plan you can run analyses of up to 100 000 URLs per audit. If the limit isn’t enough for you, please contact our support

• It depends on the plan you use. 

Currently, you can run 5 audits at the same time
Additionally, you can have up to 5 audits with monitoring enabled

• – It heavily depends on:
  • – ZipTie’s current queue
  • – how fast your server responds
  • – the number of features you’ve enabled

• – You can track progress in the dashboard

The easiest way to accomplish this is to create two separate audits:

1. – The first for blog pages
2. – The second for product pages

Remember that when you launch an audit in the Crawl mode, you cannot restrict URLs to specific pages only. It can be done either via the URL list or Sitemap mode (just remember to paste URLs or sitemaps containing blog pages or product pages only).

• – If you choose the Sitemap mode, ZipTie will analyze 100k URLs randomly chosen out of 100 sitemaps
• – If you choose the Crawl mode, ZipTie will run a crawl and stop it when it reaches 100k URLs. Then it extracts only indexable URLs

• – The cost of an Audit is determined by two factors:
  • – the number of URLs
  • – set of enabled features

• – The base cost is 1 credit per 1 URL
• – Enabling Inspection Mode increases the cost by 1 credit per URL (total 2 credits per URL)
• – Enabling JavaScript Rendering increases to cost by 1 credit per URL (total 3 credits per URL)
• – If fewer URLs are found than specified, the surplus credits will be returned to your account after the check is finished

There is no one to rule to fix them all. We try to share our knowledge about the topic based on our research and experience to make fixing these issues easier.

Here are a few of our articles that you may find helpful:

• – Index Coverage Statuses finally explained. In the article, Tomek Rudzki explains the causes of the most popular indexing issues & how to fix them
• – Ultimate Guide to Indexing SEO – just about everything you need to know about indexing condensed in a single article

If you need professional indexing consulting, feel free to contact us!

• It seems you have indexing issues. Use ZipTie to diagnose your indexing problems.