The tool stores a name and a sitemap address for each company. On its first successful check, it creates a baseline of the URLs it finds.<\/p>\n\n\n\n
That baseline matters. Importing a website with several thousand pages should not create several thousand \u201cnew\u201d discoveries. Those pages are the starting point. Future checks compare against them.<\/p>\n\n\n\n
When an unfamiliar URL appears, the tool marks it as new. When a known URL reports a later modification date, it appears as an update.<\/p>\n\n\n\n
The result is a feed that can be viewed across all monitored companies or narrowed to one competitor.<\/p>\n\n\n\n
A new service page, an industry-specific landing page, or a cluster of articles can become a useful research lead. Each still needs to be opened and interpreted.<\/p>\n\n\n\n One sitemap can mean many files<\/strong><\/p>\n\n\n\n A sitemap address does not always lead to a list of pages. It can point to an index containing separate maps for articles, services, categories, or other sections.<\/p>\n\n\n\n The importer follows those nested maps and combines their URLs into one snapshot. It also supports compressed sitemap files and multiple starting maps for the same company.<\/p>\n\n\n\n This became an important part of the build. A monitor can appear to work while quietly missing most of a website if it reads only the first file.<\/p>\n\n\n\n There are two different versions of \u201crecent\u201d<\/strong><\/p>\n\n\n\n A page discovered today may have existed for months. A page that appeared in yesterday\u2019s scan may report a modification date from this morning.<\/p>\n\n\n\n Those are different events, so the feed keeps separate dates for first discovery and the modification time supplied by the sitemap. It also records when an update was detected.<\/p>\n\n\n\n The interface lets you sort by those dates and apply a time filter to the selected one.<\/p>\n\n\n\n This makes it possible to ask more precise questions: what has the tool recently discovered, or what does the website say it recently changed?<\/p>\n\n\n\n Neither date should automatically be treated as a publication date.<\/p>\n\n\n\n Most of the interface is about reducing noise<\/strong><\/p>\n\n\n\n Collecting URLs quickly creates a second problem: deciding which ones deserve attention.<\/p>\n\n\n\n The current version has three small controls that make the feed easier to use.<\/p>\n\n\n\n A new-page marker can be cleared after review. A hide action removes an unhelpful URL from the normal feed and keeps it hidden through later updates. A heart saves an interesting page to a separate collection.<\/p>\n\n\n\n Saved links remain accessible even if the page later disappears from the sitemap. That preserves the research reference, although it does not guarantee the original page will remain available.<\/p>\n\n\n\n These controls help turn a stream of changes into a manageable reading list.<\/p>\n\n\n\n Checking less often<\/strong><\/p>\n\n\n\n Once the watchlist grew, repeatedly scanning the same sources added little value.<\/p>\n\n\n\n Checks now have a minimum interval of twelve hours per competitor. The limit applies to manual requests, automatic checks, and scheduled runs. Recently checked sources are skipped before their sitemaps are downloaded again.<\/p>\n\n\n\n For this version, that is a practical balance between noticing changes and repeatedly processing the same data.<\/p>\n\n\n\n What the signals actually mean<\/strong><\/p>\n\n\n\n Sitemap data has limits. Some websites omit modification dates. Others update them broadly, including after changes that have little editorial significance. A newly discovered URL may be an old page that was only recently added to the map.<\/p>\n\n\n\n The tool currently compares URLs and reported dates. It does not compare page text or establish why a company made a change.<\/p>\n\n\n\n A group of new pages about one industry might suggest a new commercial focus. It might also be a routine content project. The feed provides a reason to investigate; the interpretation still requires context.<\/p>\n\n\n\n The working prototype now has the core loop: collect, compare, review, hide, and save. The next question is how much useful research that loop produces over time\u2014and whether the saved discoveries help reveal patterns that occasional browsing would miss.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Checking competitor websites is easy to start and difficult to maintain. You open a few tabs, look through service pages,…<\/p>\n","protected":false},"author":1,"featured_media":770,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[878],"tags":[],"class_list":["post-768","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-in-progress-build"],"yoast_head":"\n![\"\"](\"https:\/\/basein.dev\/blog\/wp-content\/uploads\/2026\/11\/\u0417\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u043d\u044f-ChatGPT-1-\u043b\u0438\u0441\u0442.-2026-\u0440.-11_51_57-1024x798.png\")
<\/figure>\n\n\n\n