Commissioned Research
Top 10 Best Site Submission Software of 2026

GITNUXSOFTWARE REVIEW

Digital Marketing

Top 10 Best Site Submission Software of 2026

Compare site submission software options and map tradeoffs for agencies, local teams, and marketers using tools like Moz Local.

19 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Site submission software centralizes directory and aggregator publishing so local SEO teams can manage listing data at scale, run automated outreach loops, and track what gets provisioned where. This comparison helps teams weigh automation throughput against control surfaces like configuration, API access, audit logging, and schema alignment when tools differ in how they handle citations and submission workflows for local search.

Yext is the best choice for agencies managing ongoing local listings across many clients because its entity-based publishing pairs API automation with governance controls for repeatable, controlled syndication, while BrightLocal fits SMB and multi-location teams that want citation submissions tied to consistency monitoring outputs.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Yext

Entity-based location publishing with API automation and administrative governance controls for multi-client workflows.

Best for: Fits when agencies manage ongoing local listings with API automation and governance.

2

BrightLocal

Editor pick

Citation management links submission actions to location records and ongoing consistency monitoring outputs.

Best for: Fits when agencies run recurring local listings programs and need submission plus monitoring in one workflow.

3

Moz Local

Editor pick

One configured NAP and business profile drives updates across partner directories and surfaces listing alignment gaps in reporting.

Best for: Fits when agencies and local marketers need ongoing local citation submission and update management for multiple locations.

Comparison Table

1
YextBest overall
enterprise
9.5/10
Overall
2
8.7/10
Overall
3
8.6/10
Overall
4
8.4/10
Overall
5
8.0/10
Overall
6
7.8/10
Overall
7
enterprise
7.5/10
Overall
8
7.0/10
Overall
9
6.9/10
Overall
10
vertical specialist
6.5/10
Overall
#1

Yext

enterprise

Enterprise listings management platform that submits business data to a network of directories and search engines.

9.5/10
Overall
Features9.5/10
Ease of Use9.5/10
Value9.5/10
Standout feature

Entity-based location publishing with API automation and administrative governance controls for multi-client workflows.

Yext is a strong fit when submissions are part of an ongoing listings program that includes local directory distribution and channel-specific publishing rules. The platform’s automation and API support help route changes into connected syndication targets and keep internal teams aligned on what was sent and when. Governance features support multi-account collaboration through scoped access controls and audit-style change visibility.

A tradeoff is that Yext’s workflow assumes structured business entities and prefers updates through its management layer rather than one-off URL submissions. Agencies that need rapid, ad-hoc crawler directives or lightweight index pings for many unrelated domains may find the setup overhead higher than basic submission tools. Yext works best when location data is the core asset and submissions happen repeatedly with controlled quality checks.

Pros
  • +Location-first publishing workflow with controlled syndication behavior
  • +API-driven automation for repeatable update cycles across channels
  • +Role controls and change visibility for agency-style collaboration
  • +Queue-style processing for planned publishing and batch updates
Cons
  • –Best results require upfront modeling of locations and entities
  • –Not geared for one-off submissions across unrelated domains
  • –Complex governance workflows can slow small changes
  • –Advanced configuration can increase operational overhead
Use scenarios
  • Local SEO agencies

    Manage multi-location listings updates

    Fewer mismatched citations

  • Digital marketing ops teams

    Automate submissions from systems of record

    Less manual publishing work

Show 2 more scenarios
  • Brand data stewards

    Standardize NAP across locations

    Higher data consistency

    Use governed entity updates to keep business name, address, and phone consistent.

  • Enterprise rollout teams

    Control approvals before publishing

    Lower risk of bad edits

    Apply role permissions and track updates so clients and internal reviewers stay aligned.

Best for: Fits when agencies manage ongoing local listings with API automation and governance.

#2

BrightLocal

SMB

Local SEO platform offering citation building and directory submission for businesses.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Citation management links submission actions to location records and ongoing consistency monitoring outputs.

BrightLocal centers on local business management, so site submission is usually bundled into citation management, monitoring, and reporting rather than offered as a bare submission queue. The workflow connects listing targets to location records, and the platform keeps submission outcomes tied to those records for later verification. Multi-location agencies can coordinate execution across clients while retaining a shared operational view across sites.

A key tradeoff is that the platform prioritizes local citations and local SEO operations over low-level crawler controls like robots directives or direct indexation requests. BrightLocal fits best when submissions are part of an ongoing local listings program with repeated checks, not when one-time technical submission tasks dominate.

Pros
  • +Multi-location workflow ties submissions to client location records
  • +Local citation management pairs execution with consistency monitoring
  • +Bulk operations reduce manual work across large location rosters
  • +Agency-style reporting supports client deliverables from one workflow
Cons
  • –Coverage skews toward local citations more than generic URL submissions
  • –Advanced governance needs planning for multi-user, multi-client work
  • –Less direct control over crawl directives than developer-focused tools
  • –Some submission steps depend on downstream directory behaviors
Use scenarios
  • Local SEO agencies

    Manage multi-client citation submissions

    Cleaner reporting for deliverables

  • Multi-location brands

    Standardize listings across store locations

    More consistent NAP presentation

Show 1 more scenario
  • Local marketing teams

    Coordinate monthly listing cleanup

    Fewer manual spreadsheet updates

    Use monitoring outputs to target the specific locations that need listing updates.

Best for: Fits when agencies run recurring local listings programs and need submission plus monitoring in one workflow.

#3

Moz Local

SMB

Listing management tool that distributes business data to major directories and aggregators.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

One configured NAP and business profile drives updates across partner directories and surfaces listing alignment gaps in reporting.

Moz Local focuses on local citation management by mapping business listings to consistent NAP data and then managing submission and updates across partner directories. The workflow centers on verification-ready business information, so changes propagate through the directory network instead of relying on manual site-by-site edits.

Moz Local also supports reporting that shows which listings exist and how they align with the configured business profile. Where teams need more than submission, the admin side supports multi-location organization and ongoing governance of listing state.

Pros
  • +Directory network updates driven from one business profile
  • +Listing state reporting that highlights mismatches and missing entries
  • +Multi-location organization supports larger local portfolios
  • +Workflow reduces repetitive manual edits across directories
Cons
  • –Less suited for agencies needing highly custom submission formats
  • –Advanced control over per-directory rules needs operational discipline
  • –API automation is narrower than citation-focused alternatives
  • –Submission coverage varies by directory integration availability
Use scenarios
  • Multi-location marketing teams

    Propagate NAP updates in bulk

    Repeatable profile maintenance

  • Local reputation managers

    Review activity by location

    Central review visibility

Show 2 more scenarios
  • Local SEO agencies

    Maintain directory profiles for citations

    More accurate citations

    Agencies keep business information aligned across partner directories as part of citation building and local visibility work.

  • Location data governance teams

    Standardize update practices

    More consistent location data

    Teams centralize location information so directory changes follow consistent, repeatable governance routines.

Best for: Fits when agencies and local marketers need ongoing local citation submission and update management for multiple locations.

#4

Whitespark

SMB

Local citation building and submission tool focused on improving local search visibility.

8.4/10
Overall
Features8.4/10
Ease of Use8.5/10
Value8.3/10
Standout feature

Submission outcome tracking tied to batch requests for follow-up and reporting across many URLs and targets.

Whitespark targets local search submission workflows with tooling built around citation and indexation management rather than generic URL posting. It supports sitemap submission via pinging and offers structured automation for submission batches across multiple URLs.

Pros
  • +Batch workflow design for managing many submission targets consistently
  • +Submission outcome tracking supports follow-up and exception handling
  • +Sitemap and ping workflows align with crawler indexation requests
  • +Automation-friendly campaign structure reduces repetitive manual work
Cons
  • –Coverage is narrower than general-purpose local citation suite workflows
  • –Queue management and audit details require disciplined process setup
  • –Advanced handling of edge cases can add operational overhead
  • –Extensibility depends on how Whitespark structures campaign inputs
Use scenarios
  • Local marketing teams

    Run repeatable citation submission batches

    Repeatable submission workflow

  • SEO agencies

    Report local indexing request outcomes

    Client-ready operational reporting

Show 2 more scenarios
  • Local SEO practitioners

    Validate changes via submission batches

    Clearer change impact

    Practitioners compare local visibility movement after optimization by coordinating structured submission workflows for affected pages.

  • In-house local SEO

    Detect duplicate directory listing issues

    Reduced listing conflicts

    Teams use submission workflows to identify conflicting or duplicate directory entries that can distort local search signals.

Best for: Fits when agencies run recurring local submission campaigns and need submission tracking with repeatable batch workflows.

#5

Ontolo

SMB

Link prospecting and submission workflow software for SEO outreach teams.

8.0/10
Overall
Features8.0/10
Ease of Use8.0/10
Value8.0/10
Standout feature

Submission queue logging with API and webhook-style status handling for high-volume agency workflows.

Ontolo is designed for managing repeated crawl-access requests and site discovery tasks across many destinations, rather than issuing one-off form submissions. A typical workflow queues URLs or feeds, applies destination-specific settings, and records submission outcomes for later indexing verification. Agencies can use its automation and API options to connect existing campaign systems and to scale batching and scheduling without manual coordination.

Pros
  • +API-based automation for batching and scheduling submission workflows
  • +Per-destination configuration with tracked submission status logs
  • +Role-based access supports multi-client agency governance
  • +Webhook-ready task handling for pipeline status updates
Cons
  • –Higher setup overhead than form-based submission tools
  • –Indexing success is not guaranteed despite delivery tracking
  • –Some workflows require consistent URL or sitemap input hygiene
  • –Complex client routing can add operational overhead
Use scenarios
  • SEO agencies

    Automate client URL and sitemap requests

    Faster turnaround with audit history

  • Technical SEO teams

    Coordinate indexed updates after releases

    More consistent post-deploy crawl requests

Show 2 more scenarios
  • Marketing operations teams

    Integrate submission steps into pipelines

    Less manual queue management

    Use the API to provision tasks from internal campaign systems and synchronize status.

  • Agency platform engineers

    Centralize submission governance

    Clear accountability across teams

    Apply RBAC controls and audit visibility across multiple agency client workspaces.

Best for: Fits when agencies need governed, API-driven submission automation across many client URLs.

#6

Synup

SMB

Listing management and submission platform distributing business information across directories.

7.8/10
Overall
Features7.8/10
Ease of Use7.9/10
Value7.7/10
Standout feature

Location-level submission tracking paired with ongoing listing monitoring for NAP consistency outcomes.

Synup targets local citation and submission workflows through tooling that tracks where businesses are listed and what changes were made. It centralizes submission tasks, manages updates across listings, and supports ongoing monitoring of NAP consistency outcomes rather than treating submissions as one-off actions.

Pros
  • +Submission workflow tracking ties changes to specific locations
  • +Ongoing listing monitoring supports NAP consistency improvement loops
  • +Batch-oriented operations fit high-volume local citation programs
  • +Governed location records reduce accidental cross-location updates
Cons
  • –Depth varies by destination type, which can limit end-to-end automation
  • –Setup discipline is required to maintain consistent location data inputs
  • –Queue visibility can feel task-level rather than publish-system-level
  • –Some advanced handling needs tighter internal process alignment
Use scenarios
  • Retail franchise operations

    Apply location record changes

    More systematic updates

  • Multi-location marketing operations

    Keep directories and maps updated

    More consistent location info

Show 2 more scenarios
  • Reputation teams

    Monitor reviews and manage responses

    Easier review coordination

    Teams monitor reviews by location and route or manage response responsibilities in a shared workflow.

  • Local SEO agencies

    Run recurring client listing work

    Location-based client organization

    Agencies group listing, review, citation, and ranking tasks by location with repeatable reporting workflows.

Best for: Fits when agencies manage many locations and need governed submission workflows with follow-up monitoring.

#7

Uberall

enterprise

Location-based marketing platform with directory listing submission and management.

7.5/10
Overall
Features7.5/10
Ease of Use7.5/10
Value7.5/10
Standout feature

Location change governance with API-driven workflow control across distributed business listings destinations.

Uberall focuses on local directory and listing workflows where agencies need submission at scale plus ongoing updates for location data. The core capabilities include business profile distribution controls, structured location management, and audit-friendly changes across multiple destinations.

Pros
  • +Strong automation and API surface for managing high-volume location submissions
  • +Role-based access supports multi-person agencies and client operations
  • +Change tracking and reporting support audit trails for listing edits
  • +Built for ongoing distribution and update workflows, not one-time drops
Cons
  • –Setup takes effort to map destinations and align location fields consistently
  • –Submission scheduling and batch behavior can require careful operational QA
Use scenarios
  • Local web marketing teams

    Publish controlled location pages

    Consistent local destinations

  • Local SEO agencies

    Manage client location portfolios

    Repeatable client operations

Show 2 more scenarios
  • Field marketing teams

    Run location-level campaign tasks

    Controlled campaign execution

    Teams assign location tasks and manage local content or campaign execution through approval workflows.

  • Reputation and customer experience teams

    Handle reviews with location-aware routing

    More consistent responses

    Reputation teams route, moderate, collect, and respond to reviews using location-based workflows.

Best for: Fits when agencies manage many locations and need governed, API-driven submission and ongoing updates.

#8

Money Robot Submitter

SMB

Automated SEO software for link building and content submission across Web 2.0 platforms.

7.0/10
Overall
Features7.0/10
Ease of Use7.0/10
Value7.0/10
Standout feature

Project-based batch submission with built-in retries and submission log tracking for queue-level visibility.

Money Robot Submitter targets search engine submission workflows with automated URL submission and batch project runs. It manages large submission queues through configurable submission sources and repeated campaigns against saved targets.

Pros
  • +Batch submission projects with repeat runs and adjustable schedules
  • +Submission log output to track what was queued and attempted
  • +Source selection supports directory-style and URL-style submission workflows
  • +Per-campaign retry behavior for failed submission attempts
Cons
  • –Limited audit-grade governance controls for multi-user teams
  • –API surface for external automation and provisioning is not central to the product
  • –Coverage breadth varies by submission source and project configuration
  • –Setup discipline is required to prevent duplicate or redundant submissions
Use scenarios
  • Content marketers

    Distribute feed-based submission tasks

    Centralized feed submission handling

  • SEO managers

    Troubleshoot submission runs using logs

    Basic troubleshooting visibility

Show 2 more scenarios
  • SEO operators

    Submit large directory batches

    Less manual URL entry

    Operators submit many URLs to supported directories using reusable campaign settings and queued runs.

  • Freelance SEO specialists

    Batch-submit social profiles and bookmarks

    More consistent batch submissions

    Specialists run batch campaigns to submit to supported social bookmark and profile-style targets.

Best for: Fits when agencies need high-volume, template-based submission queues with manual oversight.

#9

RankerX

SMB

Automated link building tool for creating and submitting backlinks across diverse platforms.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

Run-based submission queue management with submission logs tied to each dispatch cycle.

RankerX manages search engine submission workflows by generating and submitting URLs in queued batches tied to publishing rules. The product supports sitemap-style inputs and can run submission cycles for ongoing indexation requests across many pages.

Pros
  • +Batch URL submission workflow with run-based tracking
  • +Queue control for scheduled submission cycles
  • +Sitemap-style ingestion for large site page sets
  • +Submission logs support troubleshooting per run
Cons
  • –Limited visibility into per-target crawl behavior
  • –Workflow configuration can require multiple run definitions
  • –Ownership and access controls are not surfaced as a first-class governance layer
  • –Automation depth depends on how inputs are structured
Use scenarios
  • Content-led SEO teams

    Queue article submissions with tracking

    Structured distribution tracking

  • SEO analysts

    Review placement logs and campaign outcomes

    Clear placement visibility

Show 2 more scenarios
  • Private site-network operators

    Coordinate interlinking batches

    Traceable outbound governance

    Operators schedule publishing and link placement across managed domains with traceable publishing batches.

  • SEO performance teams

    Correlate submissions with SERP movement

    Better campaign review context

    Teams combine submission and placement records with SERP tracking views for off-page campaign review.

Best for: Fits when agencies need controlled bulk dispatch with run logs for ongoing indexation requests.

#10

Ping-O-Matic

vertical specialist

Free ping service that notifies search engines and aggregators of blog content updates.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Batch submission with submission logs for ping requests, supporting queue-like processing of large URL sets.

Ping-O-Matic targets crawl discovery workflows by sending automated ping requests for URLs as content changes.

Pros
  • +Batch ping submission handles large URL lists without custom code
  • +Submission history enables quick audit of what was pinged
  • +Fast manual pings support ad hoc indexation checks
  • +Queue-style processing reduces operational overhead during content bursts
Cons
  • –Coverage is limited to ping-style signaling, not directory or citation publishing
  • –Advanced governance controls are not geared for multi-role operations
Use scenarios
  • SEO teams

    Send pings after URL migrations

    Centralized URL change notification

  • SEO operations teams

    Audit ping request attempts

    Better failure visibility

Show 2 more scenarios
  • Freelance SEO agencies

    Standardize batch notification steps

    More uniform operations

    Freelancers run the same batch-ping process across recurring update tasks for consistent execution.

  • Content publishing teams

    Notify engines after releases

    Repeatable publish-to-ping step

    Publishers send pings when new pages, articles, or posts go live to create a repeatable notification step.

Best for: Fits when agencies need automated ping submission for changing content URLs across multiple sites.

Conclusion

After evaluating 10 site submission software, Yext stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Yext

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Site Submission Software

How do Ontolo and Money Robot Submitter differ in queue management for batch submission?
Ontolo centralizes URL, sitemap, and webhook-driven tasks into a controlled queue and logs submission status per target. Money Robot Submitter runs project templates that drive repeated batch submission runs with configurable sources and retry behavior, so execution is organized around projects rather than an API-provisioned queue.
Which tools provide an API or webhook-style status handling for submission workflows?
Ontolo exposes an API surface for provisioning submissions and pulling status at scale, with webhook-style task signaling built around its queue. Uberall also supports API-driven configuration and workflow triggers for keeping location updates aligned across distributed listings destinations.
How does BrightLocal handle multi-location submission workflows compared with Moz Local?
BrightLocal ties submission actions to location records and then produces consistency signals for citation alignment across those locations. Moz Local centers on one configured NAP and business profile and propagates updates across partner directories while surfacing alignment gaps in reporting.
When is a ping-first workflow like Ping-O-Matic a better fit than directory-focused citation tools?
Ping-O-Matic focuses on crawl discovery signaling by automating ping requests for URLs when content changes. BrightLocal and Moz Local prioritize local citation distribution and ongoing listing consistency rather than emitting ping signals for newly updated pages.
What breaks if a team needs governed, audit-visible controls over who triggered submission runs?
Ontolo includes RBAC and audit visibility for triggered actions tied to submission logs, which supports compliance-style traceability in agency workflows. Money Robot Submitter emphasizes template-driven queue execution with submission logging, but it is not positioned around audit visibility for per-user governance in the way Ontolo is.
How do Whitespark and Synup differ in how submission outcomes are tracked?
Whitespark tracks submission outcomes tied to batch requests so teams can review what was requested and what was accepted. Synup keeps location-level submission tracking paired with ongoing listing monitoring outcomes for NAP consistency, so status can be evaluated over time beyond the initial submission.
How do Yext and Uberall model business data for multi-location publishing and updates?
Yext uses a structured content and location model to synchronize business data across connected endpoints through automation. Uberall emphasizes location change governance with API-driven workflow control across distributed listing destinations and role-based coordination.
Which tool is better for agency workflows that require repeatable campaigns across many URLs and targets?
Whitespark fits repeatable local submission campaigns because it builds batch workflows and tracks outcomes for follow-up reporting. RankerX fits queued indexation request cycles since it dispatches URLs in bulk batches tied to publishing rules and logs what happened afterward.
Where does RankerX fall short compared with Ontolo when building automation around submission status?
RankerX focuses on run-based workflow control with operational logging tied to each dispatch cycle. Ontolo is designed for API and webhook-style status handling across a centralized queue, which supports external automation that consumes per-target status updates programmatically.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Site Submission Software

We focus on what separates site submission tools in practice: how far they automate, how much control you keep over each submission, and how reliably they report outcomes. The biggest differences show up in API automation and audit visibility, plus how well the tool manages templates and workflows for repeat submissions.

Submission automation and scheduling controls

Why it matters

Submission automation and scheduling controls matter because site submission work often repeats across many pages and updates. When automation is configurable, we can reduce manual errors without losing control over what gets sent and when.

How to check

In a demo, set up a small workflow (for example, submit a sitemap-style list and a single page) and confirm you can trigger runs by schedule and by event. Ask what the system records for each run: inputs used, timestamps, and resulting status.

API and extensibility for your pipeline

Why it matters

API and extensibility matter because submission tools are usually driven by CMS events, content pipelines, or internal release workflows. A documented API surface helps us wire submissions into our existing process instead of clicking through every change.

How to check

Ask for the API documentation and try a simple call in a sandbox: create a submission job, provide the URL inputs, and fetch job results. Confirm whether webhooks or event callbacks exist for completion, and what fields return for status and errors.

Template configuration for submission types

Why it matters

Template configuration matters because different site updates often follow different rules. When templates support consistent patterns, we can keep submissions uniform across teams and environments.

How to check

Look for a place to define reusable submission templates. Create two templates (for example, one for updated pages and one for a structured list) and verify each allows distinct inputs, run frequency, and output fields.

Outcome reporting and verification evidence

Why it matters

Outcome reporting and verification evidence matters because submission success isn’t just “accepted.” We want visibility into what the tool actually submitted, what response it received, and what follow-up checks it can provide.

How to check

Run a test submission and inspect the per-item results view. Confirm you can export a report that shows input, submission time, response status, and any follow-up verification signals.

Admin controls and RBAC for submissions

Why it matters

Admin controls and RBAC for submissions matter when multiple roles touch release workflows. Clear governance reduces accidental resubmits and keeps audit trails aligned with who approved what.

How to check

Ask the demo to include multiple user roles. Verify you can restrict access to template editing, job creation, and report export, and check whether actions are attributed to users.

Red flags

  • You can only submit manually with minimal automation options
  • APIs lack job creation and result retrieval or are not testable in a sandbox
  • Results screens show “submitted” without per-item responses or exportable evidence

Fit by situation

  • If our team submits page updates frequently from a release workflow, prioritize submission automation and scheduling controls.
  • If we already have an internal pipeline that should trigger submissions, prioritize API and extensibility for your pipeline.
  • If multiple roles manage submissions and reports, prioritize admin controls and RBAC for submissions.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.