tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

WordPress Web Scraping: Turn Any URL Into Workflow Data

FlowMattic Webpage Parser module: a page URL goes in and its title, meta tags, text, links, emails and schema come out as fields for the next workflow step.

WordPress web scraping usually means a separate scraper service, a browser extension or a script you have to keep alive. The Webpage Parser module in FlowMattic does it as a workflow step: give it a URL and it returns the page title, meta tags, body text, headings, links, images, email addresses, social profiles and structured data as fields the next step can use.

It is built for marketers checking pages, agencies auditing client sites, and anyone who wants to enrich a lead or feed an AI agent with the contents of a page. The request goes out from your own WordPress server, and there is no separate scraping account to set up.

What is the Webpage Parser?

Webpage Parser by FlowMattic is a built-in action module in the visual workflow builder. Its description in the builder says it all: “Extract important data from any URL in your workflow.” You find it in the app picker under utilities, next to the other data tools.

It has two actions:

  • Parse Webpage by URL: parse any web page into JSON data, from the title down to every heading and link.
  • Get Meta Tags: return just the title, the meta description and every meta tag on the page, including Open Graph and Twitter tags.

How WordPress web scraping works in FlowMattic

  1. Add a trigger: a form submission, a new post, a webhook, a schedule or any app event.
  2. Add a step and choose Webpage Parser by FlowMattic.
  3. Pick Parse Webpage by URL or Get Meta Tags.
  4. In Enter URL to Parse, type a URL or map one from an earlier step. The field asks for a publicly accessible URL.
  5. Test the step. The parsed fields appear in the response and are available to every step after it.
FlowMattic workflow builder showing the Webpage Parser by FlowMattic step with the Parse Webpage by URL action and the Enter URL to Parse field.
The Webpage Parser step set to Parse Webpage by URL, with the page address mapped into Enter URL to Parse.

Behind the scenes, the module fetches the page’s HTML with the WordPress HTTP API and reads it with PHP’s DOM extension. Script and style tags are removed before the body text is collected, so content holds readable text rather than code. Your WordPress web scraping stays on your own server from fetch to result.

What each action returns

Parse Webpage by URL

FieldWhat it holds
titleThe page’s title tag
descriptionThe meta description
metaAll meta tags as JSON, keyed by name or property
contentThe body text, with scripts and styles stripped
schemaEvery JSON-LD block (application/ld+json) on the page
imagesEach image’s attributes, such as src, alt and data-src; root-relative paths are made absolute
emails, emails_listUnique email addresses found in the HTML, as JSON and as a comma-separated list
social_linksLinks to Facebook, Twitter, LinkedIn, Instagram and YouTube
internal_links, external_links, all_linksUnique links, split by whether the host matches the page’s host
heading_tagsEvery H1 to H6 with its tag and text

Get Meta Tags

This lighter action returns title, description and one field per meta tag, prefixed with meta-. An Open Graph image comes back as meta-og:image, a viewport tag as meta-viewport. Use it when you only need the preview data, for example to check how a link will look when shared.

Use cases

Enrich new leads with their website

A sales form asks for a company website. Parse it and save the public contact emails, social profiles and the page description next to the lead, so the person who follows up already knows what the company does.

Form submission → Webpage Parser (Parse Webpage by URL) → CRM: create contact

Catch posts published without a meta description

When a post goes live, read its meta tags from the public URL. If description or meta-og:image is empty, alert the editor before the post is shared.

WordPress: new post → Webpage Parser (Get Meta Tags) → Filter: description is empty → Slack message

Summarise articles with an AI agent

Feed the content field of a page into an AI step to produce a summary, key points or a draft social post. This works well for curating links your team shares in a channel or a form.

Webhook (link shared) → Webpage Parser → AI Agent: summarise → Email digest

Audit a client site’s heading structure

Agencies can list the pages to check in a table, parse each one on a schedule and record the heading tags, link counts and title for the monthly report.

Scheduler → WP Tables: get rows → Iterator → Webpage Parser → WP Tables: update row

Read product data from structured markup

Many shop pages publish JSON-LD Product schema with a name, price and availability. The schema field hands you that block as JSON, and the JSON Parser pulls out the values you need for a price-watch table.

Scheduler → Webpage Parser → JSON Parser → Router: price changed → Email

Collect outbound links for a support article review

Support teams can parse a help article and send external_links to an Iterator that checks each URL with an HTTP request step, then flag the ones that no longer answer.

Scheduler → Webpage Parser → Iterator → API request → Filter: error → Slack

Tips and gotchas

  • No JavaScript runs. The module reads the HTML the server returns. Pages that build their content in the browser can come back nearly empty; for those, the FlowMattic Browser module renders pages in a headless browser.
  • The PHP DOM extension is required. If your host has it disabled, the step returns a clear error asking you to contact the host.
  • Several fields are JSON strings. meta, schema, images, the link lists and heading_tags come back as JSON. Use the JSON Parser to pick one value, or an Iterator to loop through a list.
  • Internal means the exact same host. A link to www.example.com from example.com is listed as external.
  • Relative paths. Links and images that start with / are turned into full URLs; other relative forms may not resolve correctly.
  • Social links. Only facebook.com, twitter.com, linkedin.com, instagram.com and youtube.com are detected, and one link is kept per platform. Links to x.com are not picked up.
  • Email matching. The pattern expects a top-level domain of two to four letters, so an address on a longer domain ending can come back shortened. Check addresses before you send to them.
  • Scrape responsibly. Parse pages you have a right to read and respect each site’s terms.

Related features

  • FlowMattic Browser: screenshots, rendered HTML and scraping by selector for JavaScript-heavy pages.
  • JSON Parser: pull one value out of the schema, meta or images JSON.
  • Iterator: run steps once for every link, image or heading the parser found.

FAQ

Can I scrape a website from WordPress without a third-party service?

Yes. The Webpage Parser is a built-in FlowMattic module. It fetches the page from your own server and parses it there, so there is no scraping account or API key to manage.

Does the Webpage Parser handle JavaScript-rendered pages?

No. It reads the HTML the server sends and does not run scripts. For single-page apps and pages that load content in the browser, use the FlowMattic Browser module instead.

How do I scrape a page on a schedule?

Start the workflow with the Scheduler trigger, add the Webpage Parser with a fixed URL, and store or compare the results in later steps. Each run parses the page again.

Can it read Open Graph tags?

Yes. Get Meta Tags returns every meta tag with a name or property, so Open Graph tags arrive as fields such as meta-og:title and meta-og:image.

The Webpage Parser is included with FlowMattic alongside the rest of the data tools and nearly 900 integrations. See the plans and start turning pages into data your workflows can use.

More from the blog