Extractor CSS y XPath

Template audits rarely fail on headings alone. They fail on the boring fields buried in HTML: a canonical pointing at staging, a meta robots left on by mistake, a product ID in a data-* attribute, or JSON-LD that still references the old brand name. View Source on ten URLs is workable. On thirty template variants after a CMS deploy, it is not. The CSS & XPath Extractor on Scrawl fetches up to 10 URLs and runs up to 10 rules you define: CSS (cheerio), XPath (cheerio to well-formed XHTML, then a safe evaluator with limits), or regex with the same guards as Source Code Search . Output is a match table plus CSV. Raw HTML only. No JavaScript rendering. ! Flow from URL list through CSS and XPath rules to a results table When custom rules beat fixed heading tools Use the H1/H2 Extractor when the question is strictly heading hierarchy across up to 100 URLs. It is faster and opinionated for that job. Use custom CSS or XPath when: You need canonical URLs ( link[rel=canonical] or //link[@rel='canonical']/@href ) You are sampling meta robots or description tags across a launch batch You want one CSS class of links, not every anchor ( Link Extractor is the full inventory tool) You are hunting a string pattern in HTML with safe regex After you locate JSON-LD script blocks, validate them with the Schema Checker . Extraction finds the block; schema validation checks whether it parses. CSS selectors: start here CSS is the fastest path for most SEO fields: | Goal | Example rule | Attribute column | |------|----------------|------------------| | Canonical href | link[rel='canonical'] | href | | Meta description | meta[name='description'] | content | | OG title | meta[property='og:title'] | content | | JSON-LD body | script[type='application/ld+json'] | leave empty (text) |…