Elysia Tools
Navigation
Workflow Playbook
Extract source evidence, inspect links and assets, analyze metadata and query strings, and check RSS/Atom and robots.txt before reuse, migration, or release.
Hubs
This audit is useful when an existing page, document, feed, or URL list will be reused, migrated, or published. Save an authorized snapshot and state the destination, expected fields, domains, query policy, feed endpoints, and robots variants. The result should be a traceable decision record, not a promise about page quality or search visibility.
Start with HTML attributes, image sources, and metadata so href, src, lazy-loading references, Open Graph fields, and structured data are not missed. Branch for the material you actually have: export tables to CSV, strip tags for a readable text view, or extract Markdown links. Keep raw and derived outputs together with their source location.
Once the inventory exists, run static Markdown checks, deduplicate HTTP and HTTPS URLs, and group domains. Parse path, fragment, and query values next. Classify tracking, filtering, pagination, and content-selection parameters, then record whether each one is preserved, mapped, or excluded in the proposed handoff. A static finding is not the same as a live request result.
Review the supplied RSS or Atom feed after the URL analysis so item dates, order, duplicates, and summary content can be compared with the intended output. Lint robots.txt last and test the important URLs against the stated rules. Attach the findings, scope, and untested areas to an accept, revise, defer, or block decision; do not turn this evidence into a universal SEO or ranking claim.
Workflow playbook
Preserve the supplied HTML and extract href, src, data attributes, image URLs including lazy or srcset variants, and meta, Open Graph, Twitter Card, or structured-data fields. Record the raw source alongside the extracted lists before changing anything.
Branch on the source format: export HTML tables when rows matter, create a clean-text view when tags obscure review, and extract inline, reference, and bare Markdown links. Keep each result tied to the original file or section so later checks remain traceable.
Run the Markdown checker against the extracted document to find malformed links, broken anchors, and undefined references. Then deduplicate HTTP/HTTPS URLs and group their domains so internal, external, asset, and unexpected destinations can be reviewed separately.
Parse path segments, fragments, and parameters from the URL inventory, then compare key frequency, sample values, and encoding anomalies. Mark tracking, filter, pagination, or content-selection parameters for an explicit migration or publication decision rather than silently dropping them.
For HTML, start with attributes, image sources, and metadata. For Markdown, use the link extractor; for tables, export rows to CSV; for mixed HTML text, strip tags only when a clean-text view is useful. Do not validate a guessed inventory before preserving the source evidence.
Use Markdown Link Checker for syntax, anchors, and reference definitions without network requests. Use Bulk URL Extractor and Domain Extractor to classify the URLs you have, but treat them as inventory evidence rather than proof that every destination is reachable.
After query variants are grouped, inspect the supplied RSS or Atom feed and lint the relevant robots.txt rules. These checks describe feed and crawler exposure; they do not certify page quality or predict search rankings.
Parse the supplied RSS or Atom URL/XML to review item order, dates, duplicates, and the intended Markdown summary, then lint robots.txt and test important URLs against its rules. Attach both outputs to the decision record and note any checks that were not live or authorized.