PillarMesh Audit: read the evidence before making changes

Enter a public website URL to inspect a bounded sample of HTML pages, robots.txt and sitemap resources. This guide replaces the older template-map workflow. The original tool URL continues to work.

Start with your website

1. Enter the website or landing-page URL. Niche input is not required.
2. Optionally add your context and one relevant competitor page. Context does not influence technical scoring.
3. Run the audit and check its scope, timestamp and request errors first.
4. Review priority findings with the exact source URL, proposed action and verification step.
5. Export the report and follow the 7/30/90-day plan, validating changes against actual performance data.

What the score means

The sample check score equals 100 times passed check weights divided by completed pass-or-fail check weights. Unknown and review checks are excluded. Weights are product heuristics, not Google ranking weights. The score is not domain authority, E-E-A-T, content quality, traffic potential or a ranking prediction. A high score can coexist with serious individual issues.

What is measured and inferred

• Observed: HTTP responses, returned HTML titles, headings, meta directives, declared canonicals, JSON-LD syntax and same-host links.
• Inferred: intent labels, shared topic vocabulary, duplicate-content candidates and possible contextual links.
• Unavailable: real clicks, query demand, Google indexing, ranking positions, full-site coverage, field Core Web Vitals and verified expertise.

Crawl and indexing are different

Robots.txt controls crawling. A noindex directive affects indexing when the search engine can read it. A successful fetch does not confirm indexing. Use Search Console URL Inspection to verify important URLs. The crawler stops conservatively when robots.txt cannot be verified or blocks PillarMeshAudit.

Content and competitors

Topics come from fetched titles and headings. The tool does not create a fixed 2,210-article quota or assign keyword difficulty from a formula. A competitor comparison reads only the supplied page. Terms absent from your sample are research candidates, not proof of missing site-wide coverage, search demand or competitor rankings.

Scope and privacy

The default limits are six site pages, three sitemap resources, 1,000 sitemap URLs, 18 total outbound requests and a 20-second shared fetch budget. DNS and hosting constraints can affect timing. JavaScript is not executed. Query-string URLs and common action paths are not sampled. Submitted URLs go to this site's server; the audit does not persist reports. Hosting access logs may record requests and a temporary hashed-IP rate table uses one-hour counters; expired records are pruned on later requests.

Exports and access

JSON contains the full evidence inventory and request log. CSV contains check-level evidence and fixes. Markdown contains findings and the plan. Print / PDF opens findings for printing. The site's existing account and plan controls still apply. Checklist ticks do not alter the score and are kept only for the current browser session.

How to use the plan

In 7 days, resolve verified access problems and validate the changes. By 30 days, review actual Search Console queries and improve selected pages. By 90 days, compare consistent measurement periods and decide what to maintain, revise or expand. There is no promised traffic increase or ranking timeline; manual or expert review may still be needed.

Why traffic may be low

The audit can highlight visible blockers such as crawl issues, noindex directives, weak internal discovery paths and content questions that look under-supported in the sampled pages. It still cannot prove the traffic cause on its own. Real traffic diagnosis requires Search Console and analytics.

What to do when traffic is low

• Fix confirmed crawl and indexability issues first.
• Prioritize the most important landing pages before publishing more pages.
• Connect Search Console and analytics so impressions, CTR and conversions can be measured.
• Build supporting FAQs, guides and articles around the core offer or pillar pages.
• Re-crawl after important changes and verify outcomes with real data.

What not to do if you want to avoid a traffic drop

• Do not mass-edit URLs, titles or canonicals without measurement and redirect planning.
• Do not block valuable pages accidentally with robots rules or noindex directives.
• Do not publish many near-duplicate pages or filler content.
• Do not buy spammy links or force keyword anchors.
• Do not treat a few days of fluctuation as proof of a long-term decline.

When traffic starts growing

Protect the pages and queries already working. Improve conversion paths, expand into adjacent subtopics, refresh winners regularly and merge weak overlaps. Growth usually becomes more stable when the site improves depth and quality around the winning themes instead of merely adding more URLs.

Monthly improvements by website type

The in-tool traffic playbook classifies the sampled site into a likely website type and shows a month-by-month action plan. The current release includes playbooks for SaaS/tools, ecommerce, local businesses, publishers/blogs and general business websites.

FAQ, guide and article content for SEO, AEO and GEO

Traffic investigation checklist

• Check whether important pages are crawlable and index-eligible.
• Compare equal date ranges in Search Console.
• Look at page groups instead of only site-wide totals.
• Review winning pages before publishing more pages.
• Use FAQs, guides and articles to support the main topic cluster.

Suggested content stack by website type

SEO, AEO and GEO content notes

SEO needs clear titles, internal links and indexable page structure. AEO benefits from concise answers, steps, lists and definitions. GEO improves when the site has clear entity identity, first-hand examples, trustworthy references and content that is easy for generative systems to cite. The best websites usually support all three layers together instead of treating them as separate projects.

Google's noindex guidance ? Helpful content guidance ? Open PillarMesh Audit ?