RemeDocs Marketing Dashboard

Company

Context

Product

RemeDocs automates PDF accessibility remediation — converting inaccessible PDFs into WCAG 2.1 AA / Section 508 compliant documents — faster and more affordably than manual remediation, for organizations that cannot afford to fail an accessibility audit.

IT TrackWeb TrackCommunications/Marketing Track

Government (federal, state, local)

Higher Education (colleges and universities)

Updated 2026-04-21

Documents

competitor-comparisoncompetitor-comparison-2026-04-21.mdApr 20, 2026

copywriting-analysiscopywriting-analysis-2026-04-21.mdApr 20, 2026

59.3

landing-page-crolanding-page-cro-2026-04-21.mdApr 20, 2026

61

signup-flow-auditsignup-flow-audit-2026-04-21.mdApr 20, 2026

content-quality-scorecontent-quality-score-pdf-accessibility-app-complete-guide-2026-04-21.mdApr 20, 2026

62

seo-auditseo-audit-2026-04-21.mdApr 20, 2026

event-tracking-specevent-tracking-spec-2026-04-21.mdApr 20, 2026

conversion-attributionconversion-attribution-2026-04-21.mdApr 20, 2026

funnel-analysisfunnel-analysis-2026-04-21.mdApr 20, 2026

Competitors

Equidox

Last analyzed:Apr 20, 2026

CommonLook

Last analyzed:Apr 20, 2026

DocAccess

Last analyzed:Apr 20, 2026

(run competitor-comparison skill to populate this list from a report)

Edit .planning/dashboard-state.json to customize this list. Rebuild to apply.

Analytics

Traffic (Last 30 Days)

Active Users

552

Sessions

710

Pageviews

1,205

Bounce Rate

48.3%

PageSpeed Scores

Core Web Vitals

Field data from PageSpeed Insights

LCP

0 ms

Largest Contentful Paint

Pass

FCP

0 ms

First Contentful Paint

Pass

TBT

0 ms

Total Blocking Time

Pass

CLS

0.00

Cumulative Layout Shift

Pass

SEO Health

Meta TitlePass
Meta DescriptionPass
Canonical URLPass
LanguagePass
Mobile FriendlyFail
Image Alt TagsPass
Internal LinksPass
Word CountManual
ReadabilityManual

Actions Feed

24

CRO Findings9

**Add Equidox to the homepage comparison table** — The "How we compare" table currently lists Adobe Acrobat Pro and axesPDF, not the ICP's actual alternatives. Replace Adobe Acrobat Pro with Equidox using verified data from equidox.com. Adobe is a general PDF editing tool, not a remediation competitor; its presence signals a misunderstanding of the competitive set to procurement-literate buyers. Edit: `C:\Users\Mitch\RemeDocs\website` (specific file TBD — locate the comparison table in the homepage HTML/component).

competitor-comparisonApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Build `/compare/equidox/` standalone page** — Use the brief from Deliverable 2 above. This is the highest-traffic competitor intent query that currently returns a 404. Expected gain: capture "Equidox alternative" / "Equidox vs RemeDocs" organic search traffic from government and higher-education buyers actively evaluating alternatives. All Equidox column claims require manual verification at equidox.com before launch.

competitor-comparisonApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Add a VPAT link adjacent to the comparison table** — No VPAT link or Section 508 conformance statement appears anywhere on the homepage. Procurement buyers evaluate compliance documentation at the exact moment they are viewing the comparison table. A VPAT link in that scroll zone converts procurement-track buyers who require conformance evidence before proceeding to trial or contact. If RemeDocs does not yet have a published VPAT, producing one is a prerequisite for this action and for either standalone comparison page.

competitor-comparisonApr 20, 2026

Edit .planning/dashboard-state.json to update status

**H1: Replace category label with outcome headline** — Change "Automated PDF Accessibility" to "Pass Your Next PDF Accessibility Audit — Without Manual Remediation". Serves IT persona. The H1 is the highest-leverage copy element on the page — it determines whether a compliance buyer in audit pressure reads further or exits; switching from a category label to an outcome statement directly addresses the reactive IT buyer's most urgent decision criteria.

copywriting-analysisApr 20, 2026

Edit .planning/dashboard-state.json to update status

**VPAT: Add procurement trust signal above the fold** — Change [absent] to "A VPAT 2.4 Accessibility Conformance Report is available for enterprise and procurement evaluation." Serves IT persona. Government and higher-ed IT buyers run vendor checklists; VPAT availability is a binary pass/fail criterion in procurement evaluation, and its absence from the page currently eliminates RemeDocs from consideration before the buyer reads any other copy.

copywriting-analysisApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Primary CTA: Name the output, not the action** — Change "Start free" to "Remediate Your First PDF Free". Serves Web persona. Web-track buyers on a redesign or go-live deadline need to see the output (a remediated PDF) in the CTA to understand what they are committing to; "Start free" creates ambiguity that produces hesitation at the highest-intent moment on the page.

copywriting-analysisApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Add a VPAT/ACR availability statement to the homepage hero or trust-signal section** — Edit the homepage (`index.html` or equivalent) to add: "VPAT 2.4 available upon request — [Request VPAT]" linked to the contact form or a dedicated compliance documentation page. This directly addresses the single largest procurement disqualifier: government and higher-education buyers cannot proceed without VPAT documentation. Expected impact: lifts Compliance Trust Signals from 30 to approximately 50–55, and directly enables enterprise pipeline progression for government buyers currently blocked by this gap.

landing-page-croApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Replace the H1 with an outcome-focused compliance headline** — Edit the homepage H1 from "Automated PDF Accessibility" to a buyer-outcome statement such as "Remediate Your Entire PDF Library Before Your Audit Deadline" or "Section 508 Compliant PDFs, Automated at Scale." Keep the current H1 language as a supporting descriptor below. Expected impact: lifts Value Proposition Clarity from 62 toward 78–82 and improves first-impression clarity for the primary ICP (IT/government buyers arriving from Section 508 or audit-deadline search queries).

landing-page-croApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Add a PAC 2024 checker result screenshot to the "How does automated PDF remediation work?" section** — Insert a before/after image showing a real PDF: original state (failing PAC 2024 with critical errors listed) vs. remediated state (PAC 2024 pass, zero critical errors). This single element simultaneously addresses the primary objection ("does the output actually pass?"), adds Tier 2 WCAG testing evidence, and adds Tier 3 testing tool transparency. Expected impact: lifts Objection Handling from 52 toward 68–72, and moves Compliance Trust Signals Tier 2 from 3/5 to 4/5.

landing-page-croApr 20, 2026

Edit .planning/dashboard-state.json to update status

Content Suggestions6

**Rewrite the RemeDocs tool entry in the comparison section** — Replace "RemeDocs provides certified remediators delivering PDF/UA-1 and WCAG 2.1 AA-conformant documents with PAC-validated output and compliance documentation—particularly relevant for scanned documents, complex financial tables, and technical publications where automated tools consistently fail" with: "RemeDocs is an automated remediation platform for PDF/UA-1 and WCAG 2.1 AA conformance. It processes batch document libraries without per-file manual work, validates output against PAC before delivery, and provides a VPAT 2.4 for procurement requirements. Suited to organizations with deadline pressure and large PDF backlogs." Expected impact: corrects product misrepresentation, adds the automated/batch differentiator, brings brand voice into alignment. Estimated score improvement: +6–8 pts across D2 and D3.

content-quality-scoreApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Add a conversion section at the end of the post** — After the Key Takeaways block, add: "## Meeting the April 24, 2026 Deadline / Organizations with large PDF libraries and limited time before ADA Title II compliance deadlines can submit documents to RemeDocs for automated remediation. Output passes PAC with zero critical errors. [Request a demo] or [Start a free trial]." Align the CTA to the reader's likely track (IT → demo/contact; Web or Comms → free trial). Expected impact: +2–3 pts on D2 (buyer relevance moves from 5 to 7+) with a properly matched CTA.

content-quality-scoreApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Remove or source both quantitative claims in the FAQ and Key Takeaways** — Either (a) find and link a published source for the 70% PAC failure rate and the 60–80% cost reduction figure, or (b) replace both with qualified language as described in Issue 3 above. Then add [VERIFY BEFORE PUBLISHING] inline to any remaining quantitative claims not in the proof points list. Expected impact: +5 pts on slop score, removes compliance accuracy risk if a buyer or auditor questions the source.

content-quality-scoreApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Create a dedicated VPAT/ACR documentation guide** — New post at slug `vpat-acr-documentation-government-education`. This cluster has zero coverage and VPAT documentation is a mandatory procurement requirement for IT track buyers evaluating RemeDocs for government or university contracts. A post covering what a VPAT is, how to read a VPAT for PDF remediation, and what RemeDocs' ACR covers directly addresses the highest-authority procurement objection. Expected impact: fills the only zero-coverage cluster that directly maps to the IT track's decision criteria and positions RemeDocs ahead of competitors in procurement searches.

seo-auditApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Refresh `ada-title-ii-deadlines-government-agencies`** — This post covers ADA Title II compliance deadlines, which are among the most time-sensitive regulatory topics in the corpus. At ~461 days old (published 2025-01-15), it predates the DOJ final rule implementation timeline and any subsequent agency guidance issued in 2025–2026. Specific changes: update deadline dates, verify current DOJ enforcement posture, confirm the April 2026 compliance date language for public entities under 50,000 population, and add a section addressing what happens when an agency misses the deadline. Expected impact: restores credibility with compliance officers who check dates before citing content in corrective action plans.

seo-auditApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Refresh `doj-28-cfr-part-35-pdfs`** — DOJ 28 CFR Part 35 is the regulatory citation underlying ADA Title II digital accessibility requirements. At ~425 days old (published 2025-02-20), this post covers the regulation that has been most actively enforced and clarified during the intervening period. Specific changes: verify current CFR text matches post citations, add enforcement examples from 2025–2026 if available, update any settlement or guidance references. Expected impact: a stale CFR citation in a compliance post destroys credibility with legal and procurement readers who will check primary sources — refreshing this is a defensive credibility action as much as an SEO action.

seo-auditApr 20, 2026

Edit .planning/dashboard-state.json to update status

Analytics Insights9

Install the Plausible script tag on all pages that lack it (or the shared layout partial if one exists) — required before any events can fire. Check each page individually if no shared partial is found. Start with `index.html`, `contact/index.html`, and `pricing/index.html`.

event-tracking-specApr 20, 2026

Edit .planning/dashboard-state.json to update status

Add `contact_form_submit` to the contact form submit button using the CSS class method — this is the highest-priority conversion event because it signals enterprise demo intent, which is the primary RemeDocs conversion goal. **On remedocs.com, there is no contact form — add the CSS class to the contact email `<a>` tags in `contact/index.html` instead, and register the goal as `contact_email_clicked` in Plausible.**

event-tracking-specApr 20, 2026

Edit .planning/dashboard-state.json to update status

Register all 3 primary goal names in the Plausible Dashboard → Goals before testing — `contact_form_submit` (or `contact_email_clicked`), `trial_signup`, `purchase_completed` — events fire silently without matching registered goals and will not appear in analytics.

event-tracking-specApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Tag all SDR outbound emails with UTM parameters** — Phantom SDR and AI SDR Agent campaigns must include `utm_source` and `utm_campaign` on every link to remedocs.com. Without this, outbound-driven traffic appears as "direct" and attribution is impossible.

conversion-attributionApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Implement the event-tracking-setup spec** — add Plausible tagged events to pricing and contact page CTAs. This enables measuring actual conversion intent, not just page visits.

conversion-attributionApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Re-run this report after events are firing** — with 2-4 weeks of event + UTM data, this report can produce HIGH confidence last-touch attribution showing which content and channels drive actual conversions.

conversion-attributionApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Implement the event-tracking-setup spec** — add Plausible tagged events to all CTA links on homepage, pricing, and contact pages. This is the prerequisite for any meaningful funnel measurement.

funnel-analysisApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Enable Tagged Events in Plausible** — Dashboard > Site Settings > Optional Measurements > Tagged Events must be toggled ON before any events fire.

funnel-analysisApr 20, 2026

Edit .planning/dashboard-state.json to update status

**Register goal names in Plausible** — After adding event tags, register each goal name (trial_signup, contact_email_clicked, pricing_cta_starter, etc.) in Dashboard > Goals. Events are silently dropped without goal registration.

funnel-analysisApr 20, 2026

Edit .planning/dashboard-state.json to update status

AI CMO Advisor

Ask about your latest report findings...