The Rankings QA Checker is a Google Docs add-on that checks blog posts and landing pages against Rankings.io style requirements before submission. It reads the open document, runs both mechanical and AI-powered checks, and returns a pass/fail compliance score with specific findings.
Run it on every Rankings.io deliverable before it leaves Lexicon. Writers run it before marking a piece ready. Editors run it again before approving for submission. If the score is below 80%, it does not ship.
| Role | When to Run It |
|---|---|
| Writers | Before marking any Rankings.io piece ready for review |
| Editors (Erin / Kathlene) | Before approving for submission. Score below 80% = send back. |
| David | Admin tasks only: API key updates, redeployment |
Each user must set the Anthropic API key once before the tool will work. You only do this once.
The score excludes manual checks, which cannot be evaluated automatically.
| Status | What It Means | Action |
|---|---|---|
| Needs Attention | Check failed. A specific note explains what was found. | Fix it and re-run. |
| Passed | Check satisfied. | No action needed. |
| Manual Review | The tool cannot verify this automatically. | Review it yourself before submitting. |
| Check | What It Looks For |
|---|---|
| Keyword in headings | Primary keyword in H1, intro, H2s, and 3-4+ H3s |
| Key Takeaways block | 3-5 standalone bullets placed immediately after the intro |
| Heading structure | Minimum 3-4 H2s and 6-8 H3s beyond the FAQ section |
| FAQ section | 3-5 questions not already answered in the body |
| Ask [Firm Name] block | Q&A block placed roughly 2/3 through the post |
| Practical guidance section | Present and framed through a legal lens |
| CTA section title | Creative title — not “Conclusion” or “Contact Us Today” |
| External links | 2+ links to .gov or official state sources Manual |
| Paragraph length | No paragraphs over 70 words |
| Banned words | No use of: expert, guarantee, deserve, maximize |
| No em dashes | No em dash characters in the content |
| No medical content | No symptoms, treatments, or anatomy explanations |
| First-person plural | “We,” “our,” and “us” used throughout |
| H3 standalone opening | Each H3 opens with a sentence that answers the implied question without the heading |
| FAQ heading format | FAQ heading includes keyword + city + attorney signal |
| Check | What It Looks For |
|---|---|
| Keyword and location in H1 | Primary keyword + location in the title |
| Intro answers core question | First 2-3 sentences directly answer what the visitor is asking |
| One primary topic | No scope creep into sub-topics |
| No filler stats | No generic city facts or location padding |
| Section standalone answers | Each section opens with a direct 2-3 sentence answer |
| E-E-A-T signals | Experience, expertise, authority, and trust signals present |
| FAQs answer real questions | Practical client questions about process, timeline, fees — not textbook definitions |
| FAQ answer length | Each FAQ answer satisfies the question within 40-60 words |
| CTAs throughout | CTAs appear early and repeat at natural stopping points |
| CTA language | Specific and action-oriented — not “Learn more” or “Contact us” |
| Local references | References add jurisdictional meaning — not keyword padding |
| No legal jargon | No jargon without plain-language follow-up |
| No year references | No phrasing that will date the content |
| Statutes flagged | Legal deadlines noted for accuracy review Manual |
| Paragraph length | Short, scannable paragraphs |
| Word count | Approximately 2,000 words (target range: 1,700-2,400) |
For each red item: read the note, fix it in the document, re-run. Do not submit until all red items are cleared and the score is 80% or above.
Each user must set the API key once. Go to Extensions > Lexicon QA > Set API Key and paste the Anthropic API key. Get the key from David before your first use.
The tool could not parse the document. Make sure the document contains actual text (not images of text) and try again. If it persists, copy the content into a new Google Doc and run it there.
Usually a temporary Apps Script timeout. Wait 30 seconds and click Run Compliance Check again.
The add-on is not installed for your account. Contact Kathlene or David.
Updating the API key
script.google.com and open the Rankings QA Checker project.Code.gs line 5: var ANTHROPIC_API_KEY = 'your-key-here';Redeploying after code changes
Any change to Code.gs or Sidebar.html requires a new deployment. Team members do not need to reinstall. Updates push automatically.
| Item | Value |
|---|---|
| Apps Script project | Standalone at script.google.com (not bound to any doc) |
| Cloud project | Rankings QA (Project #1027467661242) |
| Active deployment | Rankings QA Checker v1 |
| Deployment ID | AKfycbwgNMwGDRvQAB42AHQ3hzLQOJedWqfEShPQmlE0AAR-7LZw5uD8kqHjg7JKLC6MdulWoQ |