Electronic Signature Software for Lawyers

The H1 & Meta Tags — H1 and targeted keyword changed · title rebuilt on a KD 8 term · description cut to 158 chars · both social images were EMPTY · og:url was relative

The H1 was the single word «E-Signature», and the title, OG and Twitter metas each said something different — «E-Signatures & Document Signing», «Secure E-Signatures for Law Firms», «Fast & Secure Legal E-Signatures». None repeated the other, and none said «lawyers». The searched phrase is «for lawyers» (140 vol / KD 8); the brief's phrasing «for law firms» was checked in Semrush bulk and is literally zero volume. The nav and footer use shortname="E-Signature", so the H1 could change without touching either.

Content/e-signature/En/articlemetas.cshtml · App_Data/ServiceEntities.xml · WAS = git HEAD on 2026-09-10

@* TARGETED KEYWORD (ServiceEntities.xml) — WAS "E-Signature". Now "electronic signature software for lawyers": 140 vol, KD 8, MyCase ranks 4th. The dedicated GSC query-filter export returned ZERO impressions for it in 3 months — the page never surfaced once. The brief's "for law firms" was checked in Semrush bulk: 0 volume. "for lawyers" is what people type. *@
@* H1 — from name= in ServiceEntities.xml. WAS "E-Signature". NOW "Electronic Signature Software for Lawyers". shortname stays "E-Signature" so the Features menu and footer do not change. *@
@* INTRO PARAGRAPH — briefintro WAS EMPTY; the page opened with an image block and zero keyword copy. Now 84 words, rendered under the H1 by ServicePageSkin.cshtml the same way /ai-tools does it: "Maatdesk is electronic signature software for lawyers, built into your legal practice management software rather than bolted on..." *@

@* TITLE — 62 chars. Leads with the brief's differentiator ("Unlimited") and the primary keyword. *@
@* was: E-Signatures & Document Signing — no audience, no qualifier *@
<title>Unlimited Electronic Signature Software for Lawyers | {CenterName}</title>

@* DESCRIPTION — the brief's, verbatim, 158 chars. The old one ran ~200 chars and was truncated in the SERP. At 0% CTR on position 6.49 this was the cheapest fix on the page. Names DocuSign and Adobe Acrobat Sign as the thing the firm stops paying for. *@
<meta name="description" content="Create, send, track, and store unlimited electronic signatures directly in Maatdesk. No DocuSign or Adobe Acrobat Sign subscription and no per-signature fees." />

@* OG / TWITTER TITLE — both now equal the title tag. The social card says what the SERP says. *@
@* was og:title: Secure E-Signatures for Law Firms  |  was twitter:title: Fast & Secure Legal E-Signatures *@
<meta property="og:title" content="Unlimited Electronic Signature Software for Lawyers | {CenterName}" />
<meta name="twitter:title" content="Unlimited Electronic Signature Software for Lawyers | {CenterName}" />

@* OG / TWITTER DESCRIPTION — both now equal the meta description. *@
<meta property="og:description" content="Create, send, track, and store unlimited electronic signatures directly in Maatdesk. No DocuSign or Adobe Acrobat Sign subscription and no per-signature fees." />

@* OG:URL — WAS RELATIVE ("/e-signature"). Open Graph requires an absolute URL. *@
<meta property="og:url" content="https://maatdesk.com/e-signature" />

@* SOCIAL IMAGES — og:image AND twitter:image were BOTH EMPTY: no social preview card at all. The asset already existed on disk. *@
<meta property="og:image" content="/themes/maatdesk/images/services/e-signature/e-sign2.webp" />
<meta name="twitter:image" content="/themes/maatdesk/images/services/e-signature/e-sign2.webp" />

@* OG:TYPE — stays "article", with article:published_time 2026-02-18 and article:modified_time = file write time (the /ai-tools pattern). OG and schema.org are separate vocabularies; an "article" OG type next to a SoftwareApplication/WebPage graph is not a conflict. *@

@* HERO IMAGES — e-sign2.webp + e-sign1.webp had NO alt attribute. Alt text added, real width/height set so the browser reserves the box, fade-up animation removed (matches ai-tools commit 3ff0bbd). *@

@* UNCHANGED AND CORRECT: canonical https://maatdesk.com/e-signature · hreflang="en" only (Spanish version disabled on purpose, urlspanish="x-disabled"). *@

The finding that decided the H1 and title: the page had never said «lawyer». Every phrasing on the page was product-first («E-Signature», «Document Signing», «Secure E-Signatures for Law Firms»). The 46-keyword gap set shows the entire low-difficulty cluster is audience-first — lawyer signature 320 / KD 11, attorney signature 260 / KD 16, electronic signature software for lawyers 140 / KD 8 — and effectively all of it is held by MyCase.
The pattern that decided every meta on this page: the head terms (e-signature, electronic signature, digital signature) are informational, KD 59–61, CPC $2–4, and sit under an AI Overview. The «legal X software» terms are KD 29–36 at $19–41 CPC. The title carries the primary; the body carries the money terms.

Keyword Coverage — Was / Now — 117 rows · rows 1–78 the original table, 79–117 added in the rewrite · body 516 → 2,988 words

The negative deltas are deliberate. «signing order», «automated signature reminders» and «digital certificate» were removed because neither feature is documented anywhere — support.maatdesk.com, the brief or the existing page. «tamper proof» was replaced by «tamper evident», the variant with actual volume. A Δ in this table counts a string in visible body copy (case-insensitive, hyphens as spaces, substring); it is not a ranking signal, and higher is not automatically better. Semrush columns on rows 79+ read n/p — not pulled.

SR-GAP 46 kw vs Clio / Lawmatics / MyCase · SR-BULK 68 kw, Semrush US 2026-09-10 · GSC 2026-06-07 → 2026-09-06 · WAS = git HEAD 2026-09-10, NOW = working tree 2026-09-14

Keyword	Type	Vol	KD	CPC	AIO	MD rank	Was	Now	Δ	Note
electronic signature software for lawyers	PRIM	140	8	0.00	—	— (MyCase 4)	0	10	+10	⭐ THE NEW PRIMARY. Now the XML targeted keyword, the H1, the title, the first words of the intro and FAQ #1/#20. GSC query export: ZERO impressions in 3 months — Lawmatics 5, Clio 8
legal practice management software	SEC	4400	34	41.03	Y	n/d	0	8	+8	⭐ THE MOST VALUABLE TERM IN THE TABLE, and it existed only as a JSON-LD `applicationSubCategory` string. Now in H2 #2, first mention links home
legal document management	SEC	1600	29	34.03	—	n/d	0	6	+6	⭐ Schema-only before (featureList). Now in H2 #6, links /legal-document-management-software ×2 — see the watch item in Links
attorney signature	SR	260	16	0.00	—	— (MyCase 10)	0	7	+7	⭐ A feature card, FAQ #7 and the intro. «attorney» appeared 0× in the body before
client signature	SR	90	14	6.31	—	— (Lawmatics 26)	0	8	+8	Same card and FAQ as «attorney signature»; 0× before
legal case management	SEC	590	36	19.08	Y	n/d	0	5	+5	Meta description only before. Now 5× body, links /legal-case-management-software ×3
e-signature	PRIM	5400	59	2.02	Y	n/d	8	29	+21	The old head term. Informational; SERP: AI Overview + Reviews + PAA + Things to know. Rose with the word count, not a target
e-signatures	PRIM	390	47	2.02	Y	n/d	2	5	+3	Title, OG, schema, breadcrumb
electronic signature	PRIM	12100	61	2.18	Y	n/d	2	43	+41	Lived in FAQ answers only. Informational, AI Overview — the volume is real, the intent is not commercial
electronic signatures	PRIM	n/p	—	—	—	n/p	1	24	+23	Plural of the row above; H1, H2, body, TOC
unlimited electronic signatures	PRIM	n/p	—	—	—	n/p	0	9	+9	The brief's differentiator. Title, H2, body, TOC
electronic signature software for law firms	PRIM	0	21	0.00	—	n/d	0	0	=	⚠ THE BRIEF'S PHRASING — LITERALLY ZERO VOLUME. Checked in Semrush bulk; not used
e-signature software	PRIM	480	65	12.25	Y	n/d	0	0	=	Schema description only. KD 65 — the generic form is harder than the «for lawyers» form
digital signature	PRIM	12100	59	2.26	Y	n/d	1	1	=	Kept at 1× on purpose in the S1 opener: a real term, but encyclopedic, with a Knowledge panel
digital signatures	PRIM	90500	49	2.26	Y	n/d	1	0	−1	⚠ 90,500 VOL AND NOT A TARGET. Sitelinks + AI Overview + Video + PAA + Knowledge panel — an encyclopedic query with near-zero buying intent. Went out with the old H2
document signing	PRIM	1600	65	2.79	Y	n/d	0	0	=	KD 65 + Ads + Image pack. Was in the old title; not chased
lawyer / lawyers	AUD	n/p	—	—	—	n/p	0	10	+10	⭐ 0× before, in no heading. Now H1, title, H2, FAQ, body
law firms	AUD	6600	73	0.00	—	n/d	0	9	+9	Local pack SERP, $0.00 — a qualifier, not a target on its own
attorneys	AUD	9900	80	14.08	—	n/d	0	18	+18	Local pack — directory intent, not SaaS. Rose as audience wording, not as a target
lawyer signature	SR	320	11	0.00	—	— (MyCase 7)	0	0	=	The biggest term in the KD 6–16 audience cluster. Not placed — no sentence takes it naturally; «attorney signature» carries the cluster
lawyer signature block	SR	210	9	0.00	—	— (MyCase 43)	0	0	=	KD 9, MyCase only at 43 — the softest competitor position in the whole gap set. Not a feature this page documents
law firm signature	SR	110	7	0.00	—	— (MyCase 3)	0	0	=	KD 7
electronic signature for lawyers	SR	50	6	0.00	—	— (MyCase 2)	0	0	=	KD 6 — lowest difficulty in the gap set; the H1 phrase contains it minus «software»
case management	SEC	8100	34	4.67	Y	n/d	0	5	+5	Schema featureList only before. Belongs to /legal-case-management-software; here as link text
document management system	SEC	5400	54	14.25	Y	n/d	1	3	+2	One FAQ answer before
audit trail	SEC	1900	52	16.67	Y	n/d	5	12	+7	Best-covered commercial term before the rewrite; audit-trail field list trimmed 4× → 2× without losing the keyword
ESIGN Act	SEC	1300	60	2.15	Y	n/d	1	6	+5	Now cited to law.cornell.edu 15 U.S.C. 7001 — the ground for the «legally binding» claim the page makes five times
UETA	SEC	3600	47	0.00	—	n/d	2	6	+4	Knowledge-panel query. Cited to uniformlaws.org
tamper proof signature	SEC	n/d	14	—	—	n/d	1	0	−1	Replaced by «tamper evident» — the page said «tamper-proof» in the H3 card and «tamper-evident» in the FAQ; only one has volume
tamper evident	SEC	480	28	8.17	Y	n/d	1	3	+2	The variant with volume; «tamper-proof» now 0×
digital certificate	SEC	1900	42	6.18	Y	n/d	1	0	−1	REMOVED — feature not documented anywhere. Not a loss
automated signature reminders	SEC	n/d	19	—	—	n/d	3	0	−3	REMOVED — feature not documented anywhere. The stale Razor comment claiming it was corrected too
signing order	SEC	8100	21	4.87	Y	n/d	1	0	−1	⚠ 8,100 VOL AT KD 21 — AND REMOVED ON PURPOSE. The single biggest accidental opportunity in the copy, and the feature is documented nowhere. Claims policy wins
signature tracking	SEC	10	20	0.00	Y	n/d	2	12	+10	A feature card («Real-Time Signature Tracking») and the status labels from the support site
no account required to sign	SEC	n/d	22	—	—	n/d	0	3	+3	Card + FAQ #6
retainer agreement	DOC	1300	37	2.20	Y	n/d	1	6	+5	Single FAQ mention before; now in H2 #4 and the briefintro
engagement letter	DOC	1300	30	7.66	Y	n/d	1	6	+5	H2 #4 + briefintro
settlement agreement	DOC	1600	31	3.14	Y	n/d	2	6	+4	H2 #4
contract signing	DOC	720	23	7.28	Y	n/d	1	2	+1	KD 23 at $7.28 — body + FAQ
intake forms	DOC	880	32	6.44	Y	n/d	1	2	+1	Body + FAQ
court documents	DOC	4400	77	1.08	Y	n/d	1	2	+1	KD 77, informational, $1.08 — avoid as a target
encryption	SEC	18100	84	4.39	Y	n/d	2	3	+1	KD 84, generic, not a legal-software query. Avoid
DocuSign	CMP	n/p	—	—	—	n/p	0	9	+9	Meta description, OG, H2 #5, body, FAQ #18 — the subscription the firm stops paying for
Adobe Acrobat Sign	CMP	n/p	—	—	—	n/p	0	9	+9	Same placements as DocuSign
per-signature fee(s)	SEC	n/p	—	—	—	n/p	0	9	+9	Replaces «per document fees» (n/d vol, KD 6); meta, card, body, FAQ
built into / built-in	SEC	n/p	—	—	—	n/p	0	20	+20	The positioning word of the whole rewrite — built into the practice management software rather than bolted on
practice management software	SEC	n/p	—	—	—	n/p	0	11	+11	Superset of «legal practice management software»
Word or PDF	SEC	n/p	—	—	—	n/p	0	6	+6	Support-site fact; trimmed 3× → 2× in body during the redundancy pass
maatdesk	ENT	170	16	2.48	—	n/d	4	47	+43	Brand. Every FAQ first sentence names the subject, which is where most of the rise comes from
how can businesses adopt electronic signature software for faster onboarding?	GSC-Q	—	—	—	—	GSC pos 4.0	0	0	=	⚠ THE ONLY NAMED QUERY IN 91 IMPRESSIONS — 1 impression, US, mobile, position 4. The other 90 are anonymised
lawmatics login	NAV	1300	18	13.80	—	— (Lawmatics 39)	0	0	=	Competitor navigational — the gap export's largest row and not ours. Same for clio draft login (880), simplyagree (720), simply agree (480)

Full table: 117 rows — 70 on-page keyword rows (65–70 are schema values, not searchable), 8 rows from the data sources with no on-page match, and 39 keywords added during the rewrite. The 51 rows above are the decision-relevant ones. Body word count in the same scope: 516 → 2,988 (+2,472).
Scope, counted identically on both sides: visible body copy = article.cshtml + H1 + briefintro. Matching is case-insensitive, hyphens treated as spaces, substring (so «e signature» also counts «e-signatures»); FAQ-question rows count the literal question text. Semrush gap rows show the Maatdesk rank as «—» (confirmed not ranking); bulk rows show «n/d» because the bulk export carries no rank data.
WHERE GSC IS BLIND: 1 of 91 impressions is attributed to a named query. Every «Impr / Pos / Clk» cell in the source table except that one row and the page totals reads n/a. The page-level numbers (91 / 6.49 / 0) are the only GSC evidence there is.

What the Data Says — 46 gap keywords + 68 bulk keywords + a GSC set that is 99% anonymised · analysis of the 2026-09-10 page, before the rewrite

GSC 2026-06-07 → 2026-09-06: /e-signature 91 impressions · 0 clicks · 0.00% CTR · avg position 6.49 · «Review snippet» 69 impr at 7.01

1. The page ranks and is still invisible

91 impressions at average position 6.49 with 0 clicks across three months. Position 6.5 should produce roughly 1–2% CTR. This is not a ranking problem — the SERP listing is not earning the click. Best daily position 1.0 (06-22, 07-08, 07-27, 08-11) · worst 39 (07-29) · peak days 08-29 (11 impr, pos 7.2), 06-29 (9), 08-28 (8). Country / device: the one attributed impression is United States, mobile, position 4.

2. The bulk data explains why — every head term sits under an AI Overview THIS FINDING DROVE THE FAQ AND SCHEMA WORK

Head term	Vol	KD	CPC	Intent	SERP features
e-signature	5,400	59	$2.02	Informational	AI Overview · Reviews · PAA · Things to know
electronic signature	12,100	61	$2.18	Informational	AI Overview · Reviews · PAA · Things to know
digital signature	12,100	59	$2.26	Informational	AI Overview · Reviews · PAA · Knowledge panel
digital signatures	90,500	49	$2.26	Informational	Sitelinks · AI Overview · Video · PAA · Knowledge panel

An organic result at position ~6.5 sits below the AI Overview, the PAA block and the review carousel. 0% CTR is the expected outcome, not an anomaly. Cross-check: 76% of the page's own impressions register as a «Review snippet» appearance at position 7.01 — it is already being rendered as a rich result and still converting nothing. AI Overviews are present on 30 of the 68 bulk keywords, including every head term. With AI Overviews on every head term, correct FAQ markup is one of the few remaining ways onto the SERP above the fold — and the page's FAQPage schema belonged to /ai-tools.

3. The head terms are informational, not commercial

e-signature, electronic signature, digital signature(s) and encryption are all Intent = Informational with CPC $2.02–$4.39. «digital signatures» at 90,500 volume is an encyclopedic query with a Knowledge panel — high volume, near-zero buying intent. Chasing it would add impressions and no pipeline. It was the term in the page's only pre-rewrite H2, and it is now 0× on purpose.

4. The real commercial money was in terms the page barely used THE TOP TWO NOW CARRY H2s

Term (sorted by CPC)	Vol	KD	CPC	Where it lived on 2026-09-10	Now
legal practice management software	4,400	34	$41.03	SCHEMA ONLY (applicationSubCategory), zero on-page text	8× · H2 #2
legal document management	1,600	29	$34.03	SCHEMA ONLY (featureList), zero on-page text	6× · H2 #6
legal case management	590	36	$19.08	meta description only	5×
audit trail	1,900	52	$16.67	5× in body — best-covered of this group	12×
document management system	5,400	54	$14.25	one FAQ answer	3×
e-signature software	480	65	$12.25	schema description only	0×

The first two are the standout: 6,000 combined volume, KD 29–34 (very winnable), $34–41 CPC — and they existed on this page only as JSON-LD strings no user ever reads. Both are now in an H2 and in body copy, and both link to the page that owns the term.

5. «lawyers» beats «law firms» — the phrasing on the page was the wrong one H1 / TITLE / TARGET KW CHANGED

Phrasing	Vol	KD	Source	Who ranks
electronic signature software for lawyers	140	8	gap export	MyCase 4 · Lawmatics 5 · Clio 8
electronic signature software for law firms	0	21	bulk export	literally zero volume
e-signature for law firms	n/d	20	bulk export	below reporting threshold

The OG title said «Secure E-Signatures for Law Firms». The searched phrase is «lawyers». Separately, the dedicated GSC export for the 140-volume «for lawyers» term returned ZERO impressions in 3 months — the page never surfaced for it once.

6. The lowest-difficulty winnable cluster is the audience wording the page never said out loud

Keyword	Vol	KD	Best competitor	On the page now
lawyer signature	320	11	MyCase 7	0
attorney signature	260	16	MyCase 10	7
lawyer signature block	210	9	MyCase 43	0
electronic signature software for lawyers	140	8	MyCase 4	10
law firm signature	110	7	MyCase 3	0
attorney signatures	70	11	MyCase 5	0
electronic signature for lawyers	50	6	MyCase 2	0
attorney electronic signature	40	12	Lawmatics 3	0

= 1,200 monthly searches at KD 6–16, effectively all held by MyCase. On 2026-09-10 «law firm», «lawyer» and «attorney» appeared 0 times in the body copy and in no heading on the page. The rewrite put the primary in the H1 and «attorney signature» / «client signature» in a feature card, FAQ #7 and the intro; the «signature block» rows describe a feature this page does not document and were left alone.

7. Two accidental opportunities in the old copy — one taken, one deliberately dropped

signing order — 8,100 vol, KD 21, $4.87 — mentioned once, inside a collapsed FAQ answer. Low KD, high volume. REMOVED — the feature is documented nowhere, and the claims policy for this rewrite is «only what the brief, support.maatdesk.com or the existing page documents».
tamper evident — 480 vol, KD 28, $8.17 — mentioned once. The page said «tamper-proof» (n/d volume, KD 14) in the H3 card and «tamper-evident» in the FAQ. Now 3× «tamper-evident», 0× «tamper-proof» — the term with actual volume won. Also single mentions inside one FAQ list item on 2026-09-10: contract signing (720 / KD 23 / $7.28), intake forms (880 / KD 32 / $6.44), and settlement agreement / retainer agreement / engagement letter at 1,300–1,600 volume each, KD 30–37. The three agreement types now share H2 #4 and appear 6× each; the other two are 2× (body + FAQ).

8. The FAQ long-tails have no volume but very low KD — their value is rich results and AI Overview citation FORFEITED BEFORE, MARKED UP NOW

The 14 original FAQ questions are almost all below Semrush's reporting threshold (n/d volume), but 11 of the 14 sit at KD 14–33. They will not drive standalone traffic. Their value is FAQ rich results and being quoted in an AI Overview — which the page forfeited entirely, because the FAQPage schema it carried belonged to another page. The fix was structural, not lexical: generate the accordion and the FAQPage JSON-LD from one list so the markup matches the visible text verbatim, and open every answer with a sentence that stands on its own. Engines quote the first sentence.

9. Keyword gaps ranked by opportunity — volume × difficulty × commercial intent, and where each stands on 2026-09-14

#	Keyword	Vol	KD	CPC	On-page status (2026-09-14)
1	legal practice management software	4,400	34	$41.03	8× body, in H2 #2, first mention links home
2	legal document management	1,600	29	$34.03	6× body, in H2 #6, links /legal-document-management-software ×2
3	signing order	8,100	21	$4.87	REMOVED — feature not documented anywhere
4	lawyer signature + attorney signature	580	11	$0.00	attorney signature 7×, H3 card + FAQ #7
5	electronic signature software for lawyers	140	8	$0.00	H1, title, targeted kw, 10× body, FAQ #1/#20
6	legal case management	590	36	$19.08	5× body, links /legal-case-management-software ×3
7	contract signing	720	23	$7.28	2× (body + FAQ)
8	intake forms	880	32	$6.44	2× (body + FAQ)
9	settlement agreement	1,600	31	$3.14	6×, in H2 #4
10	engagement letter	1,300	30	$7.66	6×, in H2 #4 + briefintro
11	retainer agreement	1,300	37	$2.20	6×, in H2 #4 + briefintro
12	tamper evident	480	28	$8.17	3× «tamper-evident»; «tamper-proof» 0×
—	digital signatures	90,500	49	$2.26	AVOID — informational + Knowledge panel, no intent
—	encryption	18,100	84	$4.39	AVOID — KD 84, generic, not a legal-software query
—	attorneys / law firms	16,500	73–80	varies	AVOID — Local pack SERPs, directory intent, not SaaS
—	court documents	4,400	77	$1.08	AVOID — KD 77, informational

Eleven of the twelve ranked opportunities are now on the page in the place the data suggested; the twelfth (signing order) was removed on purpose. The four «avoid» rows total 129,500 monthly volume and none of it has buying intent a SaaS landing page can convert.

Content Changes — 516 → 2,988 body words · 6 H2 sections and 3 feature cards added · an 8-entry TOC · the platform video moved in · a redundancy pass

Template for every decision: /ai-tools — same skin, same schema convention, same section pattern. Claims policy: only what the SEO brief (SEO_Title_Unlimited_Electronic_Signatures_for_Law_Firms_Maatdesk.docx), support.maatdesk.com or the existing page documents. Every change carries a Razor comment (@* *@) in the file it touches. Every new section is built from existing classes — .service-card, .prose-card, .ai-report, .matter-dashboard — with no new styles.

Content/e-signature/En/article.cshtml · ServicePageSkin.cshtml · App_Data/ServiceEntities.xml · custom.css · 2026-09-10 → 2026-09-14

The page opened with an image block and zero keyword copy RESOLVED 09-14

briefintro was empty in ServiceEntities.xml, so nothing rendered under the H1; the first body element was two hero images with no alt attribute. briefintro now carries 84 words, rendered by ServicePageSkin the same way /ai-tools does it, opening on the primary keyword and naming retainer agreements and engagement letters. Both hero images have alt text and real width/height so the browser reserves the box (no layout shift); the fade-up animation was removed to match ai-tools commit 3ff0bbd. Under the images: an «On This Page» index (.toc-card, 8 anchors); every H2 carries a descriptive id.

Sections added — six H2s from the brief, ai-tools as the template

«What Is Electronic Signature Software for Lawyers and Why Built-In Matters?» — the primary keyword as a question, 1× «digital signature» kept in the opener on purpose NEW
«Unlimited Electronic Signatures Built Into Your Legal Practice Management Software» — the $41.03 term in a heading for the first time; first mention links home NEW · H2 #2
«How Electronic Signatures Work in Maatdesk» — the 5-step walkthrough, H4 per step. S1 had the same five steps in full; it is now a one-sentence pointer to this section NEW
«Retainer Agreements, Engagement Letters and Settlement Agreements, Signed from the Matter» — Intake / During / Resolution; the three 1,300–1,600-volume document types, 6× each NEW
«Replace DocuSign and Adobe Acrobat Sign Subscriptions with Unlimited E-Signatures» — what the firm stops paying for / what it gains. No competitor price table or savings numbers: no citable source NEW
«Legal Document Management and E-Signature in One Matter Record» — the $34.03 term, linking the page that owns it NEW · H2 #6
«Simplify Your Firm's Document Workflow with Unlimited Electronic Signatures» — the closing section, carrying the video and the trial argument NEW
The video — YouTube 08CgwLegPYc (6-months-free, 41 s) — embedded in the closing section in the skin's own .vimeo-wrapper, with a lead-in linking case management, billing, time tracking and /free-trial. Why there and not the hero: it is a platform promo, not an e-signature video; it belongs next to the trial argument NEW · VideoObject + sitemap_video.xml

Feature cards — 3 → 6, Lucide icons, no new CSS

Legally Binding, Court-Admissible Signatures — carries both external citations REWRITTEN
Connected to the Matter File REWRITTEN
Unlimited Signatures, No Per-Signature Fees REWRITTEN
Clients Sign from Any Device NEW
Attorney and Client Signature Fields — «attorney signature» 260 / KD 16, 0× before NEW
Real-Time Signature Tracking — the support site's status labels: request sent / partially signed / fully signed NEW

Headings — the eight H2s now on the page

#	H2 now	Was
1	What Is Electronic Signature Software for Lawyers and Why Built-In Matters?	The 2026-09-10 table records H2 placement for one keyword only: «digital signature(s)» (rows 3/3b, now 0×). Six of the eight current H2s were added in the rewrite; the FAQ heading was reworded to carry «Law Firms». No heading on the old page contained «lawyer», «attorney» or «law firm».
2	Unlimited Electronic Signatures Built Into Your Legal Practice Management Software — the KD 34 / $41.03 term
3	How Electronic Signatures Work in Maatdesk
4	Retainer Agreements, Engagement Letters and Settlement Agreements, Signed from the Matter
5	Replace DocuSign and Adobe Acrobat Sign Subscriptions with Unlimited E-Signatures
6	Legal Document Management and E-Signature in One Matter Record — the KD 29 / $34.03 term
7	Simplify Your Firm's Document Workflow with Unlimited Electronic Signatures
8	Electronic Signature FAQs for Law Firms

«Built-In» is hyphenated in H2 #1 and in the index (proofread pass). The index has no numbering — .toc-card ol has no list-style, same as /ai-tools, and that was left alone on purpose.

Redundancy and copy-quality pass NO KEYWORD LOST

The first draft repeated itself body-to-body. 5-step walkthrough in full in S1 AND S2 → S1 is a one-sentence pointer · audit-trail field list ×4 → ×2 · «Word or PDF» ×3 → ×2 · S5 opened with FAQ #19's sentence → rewritten · «minutes rather than days» ×2 → ×1. Trimmed with no keyword lost — the +/- column confirms it. Proofread: «How ... walks through» fixed to «The section How Electronic Signatures Work in Maatdesk walks through»; FAQ #17 parallelism; no misspellings found. Stale Razor comments corrected (a reminder claim, «seven» featureList entries). The FAQ generator had stacked a copy of its Razor comment block on every run — the page carried five copies. De-duplicated, script fixed so reruns do not stack.

Web app, not mobile app THIS PAGE IS CLEAN

FAQ #12 states «Maatdesk is a web app, so signing happens in the browser with nothing to install». There is no «mobile app» claim anywhere on the page. /facts still says «Maatdesk includes a mobile app» (pre-existing, not this page) — part of the planned site-wide web-app fix, together with the /mobile-app page. Listed under Open.

FAQ Block — 14 → 20 — the 14 originals had zero structured data · the schema on the page marked up five AI questions from /ai-tools · accordion and FAQPage now come from one list

The 14 visible FAQs carried zero structured data, and the FAQPage block at the bottom of article.cshtml was copied from /ai-tools — the @id was https://maatdesk.com/ai-tools#video, the video was «Maatdesk AI Tools for Law Firms», and all 5 FAQ entities were AI questions. No FAQ rich-result eligibility and conflicting entity signals, on a page whose every head term sits under an AI Overview. Both [HIGH] issues closed 2026-09-14.

article.cshtml · 20 accordion items · FAQPage #faq generated from the same list (rewrite_faq.py) — markup matches the visible text verbatim

The original fourteen, with what each one is worth (rows 49–62)

1What is e-signature? 110 vol · KD 38 REWORDED → «what is electronic signature software for lawyers», now FAQ #1

2Are e-signatures legally binding? 20 vol · KD 26

3Is e-signature secure? n/d · KD 32 REWORDED → «is electronic signature software secure»

4What types of documents can be signed? n/d · KD 16 REWORDED → «...legal documents... electronically»

5How does the e-signature signing process work? n/d · KD 31 REWORDED → «...in Maatdesk»

6Do clients need an account to sign? n/d · KD 19 KEPT

7Can multiple parties sign the same document? n/d · KD 27 REWORDED → «can both the attorney and the client sign the same document»

8Is there an audit trail? n/d · KD 43 KEPT

9Can I sign from my phone or tablet? n/d · KD 33 KEPT

10Are signed documents stored securely? n/d · KD 22 KEPT

11Can I set reminders for unsigned documents? n/d · KD 14 REMOVED — FEATURE NOT DOCUMENTED

12Does e-signature integrate with case files? n/d · KD 21 KEPT

13How long does it take to get documents signed? n/d · KD 67 KEPT

14Is there a limit on how many documents I can send? n/d · KD 24 REWORDED → «are electronic signatures unlimited in maatdesk»

11 of the 14 sit at KD 14–33 with no reportable volume — rich-result and AI-citation material, not traffic drivers. The source table marks rows 54, 56–58 and 60–61 as the kept originals and rows 105–117 as the thirteen new questions; the «REWORDED» labels above are inferred from which original question texts dropped to 0 and which new questions cover the same ground.

The thirteen new questions (rows 105–117) — ordered by value to a generative engine

#1What is electronic signature software for lawyers? THE PRIMARY AS A QUESTION, FIRST

#2Does Maatdesk include electronic signatures? docx

#4Is electronic signature software secure?

#5What types of legal documents can be signed electronically?

#6How does the e-signature process work in Maatdesk?

#7How do attorney signature and client signature fields work? support · «attorney signature» 260 / KD 16

#9Can both the attorney and the client sign the same document?

#10Can I track an electronic signature request? docx

#16Are electronic signatures unlimited in Maatdesk? docx

#17Does Maatdesk charge per signature? docx

#18Does my law firm still need a DocuSign or Adobe Acrobat Sign subscription? docx

#19Why should a law firm use built-in electronic signatures? docx

#20What is the best electronic signature software for lawyers? «WHAT IS THE BEST…» LAST

Order: primary keyword as a question first, trust questions, mechanics, commercial, «what is the best…» last. Folded in from the brief's nine FAQs plus support-site facts — merge fields, responsible-attorney and primary-email requirements, Word/PDF only, status labels, signature-required badge, audit log to PDF.
Every answer opens with a sentence that stands on its own and names the subject — «Yes, electronic signatures are unlimited in Maatdesk: …», not «Yes.» + explanation. Engines quote the first sentence. FAQ #12 is where the «web app, nothing to install» statement lives.

Links — outbound internal 0 → 13 to 9 pages · external 0 → 2 · inbound 5 → 11 pages · cannibalisation checked, one watch item

The page had ZERO internal links out and ZERO external citations — while making the «legally binding» claim five times with nothing behind it. Only 5 pages linked in. The Features menu and footer link here from every page, but that is generated navigation, not a contextual signal.

article.cshtml + 6 other pages · audited 2026-09-14 · each target linked once where it matters, repeats of the same URL avoided

6.1 Outbound internal — 0 → 13, to 9 unique pages +13

home — on the first «legal practice management software» /legal-case-management-software ×3 — «legal case management», 590 / KD 36 / $19.08 /legal-document-management-software ×2 — from H2 #6, the page that owns «legal document management» client portal ×2 · billing · time tracking — in the closing section's lead-in and the matter-record section /pricing — anchor «one all-inclusive plan» instead of «plan» /free-trial · the cost blog post

Placed contextually, inside sentences that already named the product. The /ai-tools lesson applied from the start: no link block, no exact-match anchor stack — 13 links across 2,988 words.

6.2 Outbound external (GEO) — 0 → 2 ESIGN ACT · UETA

ESIGN Act → law.cornell.edu 15 U.S.C. 7001 · UETA → uniformlaws.org, both in the first feature card, dofollow, new tab — the same treatment as the ABA / NIST citations on /ai-tools. The page makes the «legally binding» claim five times. Linking the primary sources is what makes an engine treat it as grounded. «ESIGN Act» 1,300 / KD 60 and «UETA» 3,600 / KD 47 rose to 6× each as a side effect.

6.3 Inbound internal — 5 → 11 pages, on existing text, varied anchors +6

switching-LPMS blog post
switching-without-disrupting blog post
implementation-checklist blog post
/pricing — feature list
/administrative-law — feature card
/legal-document-management-software FAQ #2 — one sentence added, visible + schema, so the two pages link both ways
/facts gained 3 e-signature facts — legally binding, no DocuSign subscription, connected to case files — each linking here. That page is the site's fact sheet for engines and had one line on the topic

6.4 Cannibalisation — checked, one watch item WATCH

No other page targets a signature term in title / H1 / H2 / meta; every other mention on the site is a feature bullet that links here. Watch item: «legal document management» is /legal-document-management-software's targeted keyword and appears here 6× plus one compound H2. Fine while this page's title / H1 / meta do not carry it and the section links to the owner page — both conditions hold on 2026-09-14.

JSON-LD & Entity Data — two blocks copied from /ai-tools removed · 5-node graph, every id unique, every reference resolves · FAQPage 5 borrowed → 20 real

The VideoObject and the entire FAQPage block at the bottom of article.cshtml were copied from /ai-tools. The @id was https://maatdesk.com/ai-tools#video — the duplicate-@id pair the /ai-tools report flagged sitewide, seen from the other side — the video was «Maatdesk AI Tools for Law Firms», and the five FAQ entities were AI questions. Two URLs claimed the same entity, and this page's 14 real FAQs had no markup at all.

Nodes 1–5

The graph — 5 nodes, all cross-linked

Was BORROWED FROM /ai-tools

articlemetas: SoftwareApplication with a 13-module platform featureList and 3 Offers
article: VideoObject @id ai-tools#video + FAQPage with 5 AI questions — neither describes this page

Now VERIFIED ON THE RENDERED PAGE

articlemetasSoftwareApplication #software + WebPage #webpage + BreadcrumbList

articleVideoObject #video + FAQPage #faq (20 Q&A)

wiringWebPage carries datePublished / dateModified, primaryImageOfPage, breadcrumb, video; VideoObject about → /#software, isPartOf → #webpage

org / platformreferenced by @id to the home page's nodes, not duplicated

verifiedvalid JSON, unique ids, every reference resolves, FAQ text found verbatim, embed present, assets 200

Node 5

FAQPage — 5 borrowed AI questions → 20 real ones

What changed HIGH · CLOSED 09-14

The old block marked up five /ai-tools questions; none of the 14 e-signature FAQs on the page were in it
Now #faq with 20 Q&A, generated from the same list as the accordion (rewrite_faq.py) — the markup matches the visible text verbatim, checked on the rendered page
Why it matters here more than elsewhere: with an AI Overview on every head term, FAQ rich results are one of the few remaining routes above the fold

Node 4

VideoObject — its own video, its own @id

Fixed DUPLICATE @id RESOLVED

@id/e-signature#video — was ai-tools#video

videoYouTube 08CgwLegPYc, the 6-months-free promo

uploadDate2026-02-25

durationPT41S

about→ /#software · isPartOf → #webpage

sitemapsitemap_video.xml: /e-signature entry added

Why the promo video and not a signature demo

There is no e-signature video. The platform promo is embedded in the closing section next to the trial argument, not in the hero, so the markup describes exactly where it sits and what it is

Node 1

SoftwareApplication — description and featureList rebuilt

Now SCOPE CORRECTED

E-signature-specific description — the old one was the generic platform text
10-item featureList of documented capabilities, replacing the 13-module platform list (AI Tools, Calendaring, Contact Mgmt, Time Tracking, Gmail, Task Mgmt, Client Portal, Billing, Case Mgmt, Legal Doc Mgmt, Trust Acct, Mobile App…) that the source table logs as rows 65–70, «schema values, not searchable keywords»
3 Offers with price + currency only — 6 Month Free Trial, $39/user monthly, $29/user annual; no priceSpecification, so the /ai-tools Rich Results warning does not recur here
«legal practice management software» stays in applicationSubCategory — and is now backed by 8× visible copy and an H2

Declined

aggregateRating — deliberately NOT added

The Elfsight footer widget injects review snippets client-side — the same finding as on the home page and /ai-tools.

A hardcoded rating would create two competing sources for the same claim. Note the irony: 76% of this page's impressions already render as a «Review snippet» appearance — the rating is there, and it is not what is holding CTR at zero.

Node 2 + 3

WebPage + BreadcrumbList

WebPage#webpage — datePublished 2026-02-18, dateModified = file write time, primaryImageOfPage e-sign2.webp, breadcrumb, video

BreadcrumbHome > E-Signatures (source table row 70)

og:typestays «article» — OG and schema.org are separate vocabularies, and this is the /ai-tools pattern

Deliberate Omissions & Measurement — 8,100-volume «signing order» dropped on purpose · 129,500 volume of «avoid» terms · and the numbers that will judge this work

The single biggest accidental keyword in the old copy was removed, not amplified. «signing order» (8,100 / KD 21) appeared once in a collapsed FAQ answer — and the feature is documented nowhere. Same for «automated signature reminders» and «digital certificates». The claims policy — only what the brief, support.maatdesk.com or the existing page documents — produced every negative delta in the keyword table.

DO NOT «FIX» THESE — each one is a decision with a reason, recorded so the next editor does not undo it

What was left out, and why

«signing order» (8,100 / KD 21) · «automated reminders» · «digital certificates» — DROPPED. Neither feature is documented on support.maatdesk.com, in the brief or on the page. The stale Razor comment that claimed reminders was corrected at the same time
«digital signatures» (90,500 / KD 49) — 0× on purpose; «digital signature» kept at 1× in the S1 opener. A real search term, but encyclopedic with a Knowledge panel. «digital signature for lawyers» / «digital signatures for law firms» were checked in Semrush bulk on 2026-09-14: n/d volume, KD 15 — logged, not used
«electronic signature software for law firms» — the brief's phrasing — NOT USED. Semrush bulk: 0 volume. «for lawyers» is what people type
«encryption» (18,100 / KD 84) · «court documents» (4,400 / KD 77) · «attorneys» / «law firms» (16,500, Local pack) — NOT TARGETS. They appear as vocabulary, not as headings
Competitor price table / savings numbers — NOT DONE. No citable source. The DocuSign / Adobe Acrobat Sign section says what the firm stops paying for, not how much
More FAQs or sections — NOT DONE. 2,988 words is enough. Index numbering — NOT DONE: .toc-card ol has no list-style, same as /ai-tools
aggregateRating NOT added — the Elfsight widget already injects review snippets client-side
Spanish version stays disabled (urlspanish="x-disabled"), so only hreflang="en" is emitted. NOT PLANNED — the one 2026-09-10 issue left open by design

Technical changes that carry no keyword

custom.css — one rule replaces three per-page anchor lists. h1[id], h2[id], h3[id], h4[id], section[id] { scroll-margin-top: 110px } replaces the #roi-calculator, /ai-tools and /e-signature id lists, so the next page with anchors needs nothing added. main.min.css rebuilt by the bundler
sitemap_video.xml — /e-signature entry for the video
Hero images — fade-up animation removed, width/height set, alt added
No new styles for any section, card, index or video
FAQ generator — fixed so reruns do not stack Razor comment blocks

How to judge this work — re-pulled in 4–6 weeks after deploy NOT WORD COUNT

Measure	Now (pre-rewrite window)	What movement would mean
GSC query = «electronic signature software for lawyers»	0 impressions / 92 days	The primary. Any impression is new; the page never surfaced for it once
/e-signature CTR	0.00% on 91 impr at 6.49	Title + 158-char description + FAQ rich results are the CTR levers; 1–2% is what position 6.5 should earn
«Review snippet» share of impressions	69 of 91 (76%)	If FAQ rich results start appearing, the appearance mix changes before CTR does
Search Console → Enhancements	—	FAQ, Video, Breadcrumb should all report valid items for this URL after the crawl

AND THE CAVEAT THAT APPLIES TO EVERY FIGURE ABOVE: all impression and position data in this report was exported BEFORE the work, for 2026-06-07 → 2026-09-06. Nothing here is evidence that a ranking changed. The tables show what the edits did to the PAGE, not what Google did with it — and nothing is committed yet, so the clock has not started.
Off-page is the ceiling now: Capterra / G2 / Lawyerist listings should say «unlimited e-signatures included» and link /e-signature.

Source Index — 4 keyword data sets · 4 in-repo sources of truth + 3 touched files · 2 claim sources · scan date 2026-09-10

Every figure in this report traces to one of the rows below

A. Keyword data

SR-GAPsources\e-signature\gap.keywords_2026-09-09T21_15_16.646Z.csv — 46 keywords. Semrush Keyword Gap vs Clio / Lawmatics / MyCase. Maatdesk ranks for 0 of the 46; Clio owns 33, MyCase 7, Lawmatics 7; 9,190 monthly searches unclaimed

SR-BULKdigital-signatures_encryption_bulk_us_2026-09-10_10-21-10.csv — Semrush Bulk Keyword Overview, US, 68 keywords, keyword overview only (no rank data). AI Overview present on 30 of 68

GSC-PAGEsources\e-signature\e-signature url\…Performance-on-Search-2026-09-09 (1)\ — Search Console, Web, Page contains https://maatdesk.com/e-signature, 2026-06-07 → 2026-09-06: 91 impr / 0 clicks / 6.49

GSC-KWsources\e-signature\e-signature keyword\…Performance-on-Search-2026-09-09\ — Search Console, Query = «electronic signature software for lawyers», same window — 0 impressions across all 92 days

B. On-page sources of truth — the four files this page is made of, plus three touched

Views/ServicePage/Content/e-signature/En/articlemetas.cshtml (M) — metas + SoftwareApplication, WebPage and BreadcrumbList schema
Views/ServicePage/Content/e-signature/En/article.cshtml (A) — body copy + FAQ + VideoObject and FAQPage schema
Views/ServicePage/ServicePageSkin.cshtml (S) — renders the H1 and the brief intro
App_Data/ServiceEntities.xml (X), id="e-signature" — the name attribute IS the H1, briefintro is the intro paragraph, shortname is the menu/footer label, and the targeted keyword lives here too
custom.css (C) — the single scroll-margin-top rule
sitemap_video.xml (V) — the /e-signature video entry
6 other pages — the inbound links under 6.3

C. Claim sources and external citations TWO CITED ON THE PAGE

docxSEO_Title_Unlimited_Electronic_Signatures_for_Law_Firms_Maatdesk.docx — the SEO brief; meta description verbatim, nine FAQs, the DocuSign / Adobe Acrobat Sign positioning

supportsupport.maatdesk.com — merge fields, responsible attorney, primary email, Word/PDF only, status labels, signature-required badge, audit log to PDF. See the contradiction under Open

ESIGN Actlaw.cornell.edu — 15 U.S.C. 7001, cited in the first feature card

UETAuniformlaws.org, cited in the first feature card

Nothing was asserted that none of these documents. Where the brief and the support site disagree (DocuSign), the page follows the brief and the disagreement is logged.

Status — Done vs Open

NOT COMMITTED. Everything described in this report is in the working tree. Google still reads the old page: the one-word H1, the truncated description, no social image, and a FAQPage that marks up five /ai-tools questions. Until this ships, the measurement clock has not started.

PAGE STATE 2026-09-14, end of session. Body copy 2,988 words (516 at the start) · 8 H2 sections (six added) · 6 feature cards (was 3) · 20 FAQ items (was 14) · internal links out 13 to 9 pages (was 0) · external citations 2 (was 0) · inbound internal links 11 pages (was 5) · schema 5 nodes, unique ids, every reference resolves, FAQ text verbatim · «electronic signature software for lawyers» 10× (was 0) · «lawyer / attorney / law firm» in headings yes (was none).

Scan 2026-09-10 · rewrite 2026-09-10 → 2026-09-14 · every change mirrored as a Razor comment at the point of the edit

✓ Done

✓ [HIGH] Wrong JSON-LD removed — the /ai-tools VideoObject and FAQPage are gone; the page has its own #video and a 20-question #faq
✓ [HIGH] The visible FAQs now carry structured data, generated from the same list as the accordion
✓ [MED] Hero images have alt text, width/height, and no fade-up
✓ [MED] og:image and twitter:image were EMPTY — both set to e-sign2.webp; og:url made absolute [LOW]
✓ [MED] briefintro was empty — now 84 words under the H1
✓ [MED] H1 «E-Signature» → «Electronic Signature Software for Lawyers»; targeted keyword changed to match; shortname untouched so the menu and footer do not change
✓ [LOW] Meta description ~200 → 158 chars, the brief's verbatim; title rebuilt; OG and Twitter titles/descriptions = title/meta
✓ Body 516 → 2,988 words: six H2 sections, feature cards 3 → 6, an 8-anchor «On This Page» index
✓ «legal practice management software» and «legal document management» moved from JSON-LD-only into H2s and body copy (8× and 6×)
✓ «attorney signature» / «client signature» 0 → 7 / 8 — a feature card, FAQ #7 and the intro
✓ FAQ 14 → 20, ordered for generative engines, every first sentence stands alone
✓ Internal links 0 → 13 across 9 pages · inbound 5 → 11 pages · ESIGN Act and UETA cited to primary sources
✓ Video embedded in the closing section; sitemap_video.xml entry added
✓ Redundancy pass with no keyword lost · proofread · stale Razor comments corrected · FAQ generator de-duplicated (five stacked comment copies)
✓ custom.css: one scroll-margin-top rule for all anchored headings; main.min.css rebuilt
✓ Cannibalisation check: no other page targets a signature term in title / H1 / H2 / meta

⚠ Open

⚠ NOT COMMITTED — nothing from this work is in git, and Google is still reading the borrowed schemathis is the only item that blocks every other item
⚠ After deploy: request indexing for /e-signature, /facts and the six pages that gained links; check Enhancements (FAQ, Video, Breadcrumb) in Search Console; judge after 4–6 weeks on impressions for «electronic signature software for lawyers» and CTR
⚠ «Included in the 6-month free trial» is now a stated claim on this page — confirm with the trial-terms ownerthe video lead-in and the closing section both rely on it
⚠ Support-site contradiction: support.maatdesk.com says eSignature is configured through a DocuSign popup; the brief says no DocuSign. The page follows the brief. Tell the support-site owners
⚠ Site-wide «mobile app» → «web app» fix. This page is clean; /facts still says «Maatdesk includes a mobile app» and the /mobile-app page is not fixed
⚠ Off-page is the ceiling now. Capterra / G2 / Lawyerist listings should say «unlimited e-signatures included» and link /e-signature
⚠ Watch: «legal document management» 6× + one compound H2 here, on a term /legal-document-management-software owns. Fine while this page's title / H1 / meta do not carry it
⚠ [NOT PLANNED] Spanish version disabled (urlspanish="x-disabled"), so only hreflang="en" is emitted — the one 2026-09-10 issue left open by design

TEST AFTER DEPLOY, in this order. Rich Results Test on the live URL — it confirms the 5 nodes parse, shows FAQ / Video / Breadcrumb eligibility, and shows whether the Elfsight review snippets are still being injected. Search Console → URL Inspection → Request Indexing for /e-signature, /facts and the six linking pages. Then re-pull the two GSC exports in 4–6 weeks and compare against 0 impressions / 0.00% CTR / 6.49.
Standing instruction: every change made to this page is logged in e-signature-improvements.txt as a matter of course, without being asked, and mirrored as a Razor comment at the exact point of the edit — with the brief, support-site or Semrush source it came from. Each pass appends its own section below the previous one: WHAT changed, the SOURCE relied on, the KEYWORDS reinforced with their volume and KD, and the updated open-items list carried forward. To refresh the table after the next round, re-parse both sides on the same day — «WAS» must keep meaning the git HEAD on 2026-09-10 no matter how many times the counter runs.

Electronic Signature Software for Lawyers — SEO Improvements