Build reusable client feeds from trusted RSS and Atom sources, narrow them by topic or location, apply relevance and exclusion rules, remove duplicate coverage, and publish the filtered stream through a reusable CMSPost token.
CMSPost Feed Intelligence starts with a topic or keyword and an optional location, combines multiple trusted sources, then gives the agency control over the rules that determine what is allowed into the final client feed.
Enter a topic or keyword, optionally add a city, county, state, region, or service market, and build the starting feed configuration from multiple RSS or Atom sources.
Start from any client topic or industryAdd an optional geographic focusCombine multiple RSS or Atom sourcesKeep the feed attached to the selected client workspaceControl relevance with required keywords or locations, excluded terms, source choices, content ordering, and duplicate protection so the final stream stays useful instead of noisy.
Require topic keywords or locationsExclude unwanted termsChoose content orderingRemove duplicate URLs and highly similar headlinesSave the configured feed and reuse it through a CMSPost feed token inside supported client content, pages, and layouts without rebuilding the source rules every time.
Save the feed configuration onceGenerate a reusable client feed tokenPlace the token into supported CMSPost contentUpdate the feed rules without rebuilding the page
Client Feed Configuration
Supported Source Formats
Core Intelligence Controls
Reusable Feed Token
The goal is not to dump another generic news stream onto a client site. CMSPost gives the agency a repeatable way to define the topic, control relevance, reduce duplication, and reuse the result.
Enter a topic or keyword, add an optional location, choose the source scope, and create the starting configuration for the client feed.
Combine multiple RSS or Atom sources into one client stream instead of making the entire experience depend on a single publisher.
Require keywords or locations, exclude unwanted terms, choose ordering, and remove duplicate URLs or highly similar headlines.
Save the feed once and publish the filtered stream through a reusable CMSPost token inside supported client pages and templates.
Define what the client feed should cover, combine source inputs, filter for relevance, remove duplicate coverage, and publish through a reusable token.
Build the configuration around the client once, then keep refining the source and relevance rules without rebuilding the destination page.
Start with the client's industry, service, keyword, subject, or market instead of a generic feed.
Combine multiple RSS or Atom publishers so the stream is not tied to one source or one editorial viewpoint.
Use required terms, location rules, exclusions, ordering, and duplicate protection to keep the feed focused.
Publish the saved stream through a reusable CMSPost token and update the feed rules centrally when the client's needs change.
Apply to the CMSPost Partner Program, receive your secure referral identity, and introduce qualified agencies to a platform created for their daily workflow.
Feed Intelligence is designed to give agencies control over the sources, relevance rules, duplication, and reusable publishing layer for each client feed.
