Haloscan by Sequance Make integrationAutomate Haloscan by Sequance with Make.

You get a side-by-side of your domain's keywords and those of competing sites, which is the comparison this module's name announces. It is the quickest way to spot topics rivals cover and you do not.

This one lines up search result pages for a keyword so you can see what changed or what differs between them, going by its name. Handy when a page drops and you want the context before touching the content.

A search module that looks a keyword up in Haloscan and returns what it finds. Like every search in Make, it can return zero, one or several bundles, and each following module runs once per bundle.

Synonyms of a keyword come back as a list you can drop into a brief, if the name holds. Writers get alternative wording without leaving their document, and you avoid stuffing the same phrase everywhere.

Its name points to keywords that contain or match the term you give, which widens one seed into a family of queries. Good raw material for a topic cluster.

Related queries, the ones that sit next to your main term without repeating it, are what this search should bring back. They help you decide which subtopics deserve their own section.

Close variants of a keyword, judging by the name, so you can catch spellings and phrasings that target the same intent. Useful to avoid two pages fighting for the same query.

You see which pages of a competing site perform best, as the module name promises. That tells you where a rival gets its traffic and which formats seem to work in your market.

A snapshot of a domain in Haloscan, the kind of summary you would open first when a new client arrives. The name says overview, so expect headline data rather than page-level detail.

Categories for a domain, worked out from its Google Business Profile backlinks (GMB in the module name), as far as the name tells. For local SEO, it shows how a business is positioned through the listings pointing to it.

Names of the sites competing with a domain on search, which gives you a ready starting list for any competitive study. No more building that list by hand from memory.

Several domains in one request instead of one module run per site, if the bulk in its name means what it says. That keeps a scenario shorter when you handle a whole portfolio.

A map view of the Google Business Profile backlinks pointing to a domain, going by the module name. It helps a local SEO see where those links come from geographically.

How a domain's rankings moved over time, which is the history this module is named after. You can then explain a traffic change with dates instead of impressions.

The pages of your own domain that carry the most search weight, as the name indicates. Knowing them tells you which URLs to protect during a redesign.

One Google Business Profile backlink record, if the singular in the name is accurate, rather than a full map or category view. It suits a scenario that checks one specific listing.

A timeline of a domain's pages, based on the name, so you can see which URLs appeared or disappeared from search. Useful to catch pages lost after a clean-up.

Give it a page address and it should return the keyword data tied to that URL. That answers the classic question of what a given page actually ranks for.

Data for a batch of keywords in one module run, which the bulk in its name suggests. Fewer runs mean fewer operations than looping a single-keyword module over a long list.

Highlights for a keyword, which the name leaves open: run it once to see exactly what Haloscan returns before building on it. It is the module to test, not to assume.

The main data for one keyword in a single step, the natural starting point for any brief. It is the module used in the first scenario on this page.

Questions that searchers ask around a keyword, going by the name. They make ready-made FAQ ideas and subheadings for your content.

The dates for which Haloscan holds SERP snapshots of a keyword, per the module name. You need them before asking for a comparison between two points in time.

How the result page of a keyword evolved, which pages entered and which left, if the name holds. It explains volatility better than a single ranking number.

A view of how ranking sites structure their content around a keyword, by its name. That can inspire the sections and the internal links of your own page.

Where a domain ranks for its keywords, as the module name reads. This is the classic ranking report, delivered into whatever tool you choose.

Your remaining Haloscan credit, judging by the name, readable inside a scenario. It lets a scenario check what is left before launching heavy requests.

A visibility curve for one or more domains, per its name, so you can compare how sites gain or lose ground in search. Good material for a market overview.

Expired domains you could look into, going by the name, which is useful for netlinking research or recovering a brand name. The scenario builds the shortlist, you make the call.

Going by its name, you get the keywords a single page performs best on: in short, what that URL really wins on. Where Get a Keyword Data from an URL seems to return everything tied to the address, this one seems to keep only the top performers.

Any endpoint of the Haloscan API becomes reachable from your scenario, with the same connection as the other modules. It covers what the dedicated modules leave out.

Details on an expired domain, if reveal means what it usually does in such tools, once you have spotted it in a list. It is the second step after Get an Expired Domains.

Fresh data collected for a keyword, as scrap (short for scrape) in the name suggests, rather than what Haloscan already stores. Useful when a term is new or missing.