First-party editorial evaluated for practicing-physician reviewer signals.
Google Search Central documentation specifies that the Reviews System evaluates first-party standalone content written to provide a recommendation, opinion, or analysis 1 . A physician authoring a comparative review of two CPAP machines, a clinician evaluating a new laser therapy, an editorial article on the candidacy criteria for a specific procedure. The framework explicitly does not evaluate third-party user reviews like patient testimonials posted on a service page. The two surfaces face different rules and have to be architected separately on the site.
The framework reads three load-bearing signals on first-party editorial: practicing-physician reviewer status, ABMS specialty alignment with the article topic 2 , active state license. The byline surfaces the name; the JSON-LD Physician.sameAs chain ties the name to the ABMS verification page, the NPPES NPI registry entry, and the state medical board licensure profile. Without the chain, the framework reads the byline as an unverified claim. The chain becomes the proof.
Two attributions, one editorial workflow.
The named author is the byline at the top of the article and the Article.author in JSON-LD. The medically-reviewed-by attribution surfaces alongside when a different physician reviews the work for accuracy. The pattern reads as: an SEO specialist drafts the structural copy, the named physician author authors the medical substance and reviews the draft for accuracy, and a separate medically-reviewed-by line attributes the medical review.
The named author entity carries the ABMS specialty alignment audited against the article topic. The medically-reviewed-by physician carries the secondary check. Both names link to /author/<slug>/ pages with Physician.sameAs chaining to ABMS verification, NPPES, and state medical board licensure. The architectural pattern surfaces both attributions visibly on the page (not hidden in a tooltip or stripped from the rendered HTML) so the Reviews System reads the actual editorial workflow.
Editorial content one surface. Patient testimonials another.
First-party content is what the practice authors and publishes on its own surface. Editorial articles, comparative reviews, clinician-authored case discussions, treatment overviews authored by the practice's physicians. Third-party content is what someone else submits and the practice republishes. Patient testimonials, Google reviews syndicated to the site, quote cards extracted from social media.
The Reviews System framework evaluates the first-party content for the practicing-physician reviewer signals. Third-party content gets evaluated under different criteria, including HIPAA marketing-authorization mechanics under 45 CFR 164.508 when the third-party content is patient-derived 3 . The site architecture keeps the two surfaces visibly separate: editorial content lives at /research/ or /blog/ with the byline plus medically-reviewed-by chrome; patient testimonials live on the service pages in a chrome-distinct component.
The AMA E-9.6.1 advertising-standards floor reads testimonial typicality across the practice's surface 4 . State medical boards layer their own testimonial-disclaimer rules on top (Florida's typicality language, California's Business and Professions Code rules). The disclosure pattern on the patient-testimonial component absorbs the per-state overlay.
The editorial layer is the load-bearing surface for the YMYL signal in the doctor SEO architecture at Praxis. The named author plus the medically-reviewed-by attribution plus the schema chain are what the Reviews System reads.