SEOPayment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.

Example result
robots.txt and sitemap: an online clothing store
Client: an online clothing store with filters and site search. Task: stop search engines from crawling thousands of filter and cart pages, and point them to the sitemap.
User-agent: *
Disallow: /cart
Disallow: /checkout
Disallow: /account
Disallow: /search
Disallow: /*?sort=
Disallow: /*?color=
Disallow: /*&size=
Allow: /collections/
Sitemap: https://example.com/sitemap.xml
Sitemap plan:
| File | What it lists | Pages |
|---|---|---|
| sitemap.xml | index of the files below | |
| sitemap-collections.xml | categories | 64 |
| sitemap-products-1.xml | products | 1–5,000 |
| sitemap-products-2.xml | products | 5,001–8,300 |
| sitemap-pages.xml | about, delivery, returns, blog | 41 |
Why: filter pages repeat category content and waste crawling. Products out of stock for more than 90 days come out of the sitemap but keep their page.
The client and all details are made up.
About this service
A single sitemap file holds at most 50,000 URLs, and on a marketplace or classifieds site with hundreds of thousands of listings that change daily, one giant file tells you nothing about what is indexed. We plan a sitemap index with files split by section and type, such as categories, listings by date or ID range, locations and articles, with rules for which URLs go in, how lastmod is set and how expired listings leave. The split also lets you see indexing per section in Search Console.
What is included
- What you getA sitemap plan: the index structure, each child file with its contents and size limits, inclusion and exclusion rules, lastmod and expiry rules, and a specification your developers can build from.
- Index structureChild files by section and type
- Split rulesBy date, ID range or location
- What goes inOnly canonical, indexable 200 pages
- FreshnessHonest lastmod and expired listings
- Developer specFields, limits and regeneration schedule
How it works
- 1InventoryYou list page types and counts
- 2PlanWe design the index and splits
- 3SpecYou get a plan for developers
What we need from you
A link to the site, the page types with rough counts (categories, listings, profiles, locations, articles), how often listings are added and removed, and your current sitemap URL if there is one.
We will ask you:
- Which page types does the site have, and roughly how many of each?
- How many listings are added and removed per day?
- What happens to a listing page when it expires?
- Is there a current sitemap, and how is it generated?
Compare packages
| Packages | Basic$15 | Standard$29 | Premium$55 |
|---|---|---|---|
| What is included | Up to 4 page types | Up to 8 page types | Up to 15 page types |
| Deadline | 2 days | 3 days | 5 days |
| Revisions | 1 | 2 | 2 |
| Page types planned | up to 4 | up to 8 | up to 15 |
| XML examples | Yes | Yes | Yes |
| Developer specification | Yes | Yes | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Should every listing be in the sitemap?
Only live, canonical, indexable ones. Empty category pages, duplicates and expired listings stay out, and the plan sets those rules.
Does a sitemap make Google index everything?
No. It helps discovery and lets you track indexing by section; what gets indexed still depends on page quality and links.
Do you write the generator code?
The plan includes the XML format, examples and rules. Your developers build the generator for your stack.
Did not find your answer?


