Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Include verification method within a users Site Health information

See original GitHub issue

Feature Description

Consider outputting a Search Console verification method within a users Site Health information. This would help with determining whether Site Kit was used to verify site owners or an alternate method, with alternate methods at present potentially causing disconnection issues or resulting in avoidable lengthy support topics.

Example issues with a manual verification:

A user may have their http site verified manually prior to Site Kit setup (http://wwww.example.com). Site Kit uses this existing verification and doesn’t add other variations of that domain (non www / https). If a user removes the www from their site, or makes their site https they’ll become disconnected.
Users are unable to remove their own verification at SC level as the message states that the verification file remains on their site if SK remains active. If they open a support topic the support team can determine from their SH info that SK is the verification method this notification if referring to.

Possible Flag that may be useful:

Search Console verification: Site Kit || Prior verification

If not too trivial the below would be a further improvement:

Search Console verification method: Site Kit || DNS || File upload || Existing snippet

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

A new field “Verification Status” should be incorporated into Site Kit’s Site Health section, right below “User Status”:
- If the user is not verified (i.e. Verification user option false-y), it should say “Not verified” (debug: “not-verified”).
- Otherwise, if verified through a file token (i.e. Verification_File user option), it should say “Verified through file” (debug: “verified-file”).
- Otherwise, if verified through a meta token (i.e. Verification_Meta user option), it should say “Verified through meta tag” (debug: “verified-meta”).
- Otherwise, it should say “Verified outside of Site Kit” (debug: “verified-non-site-kit”).

Implementation Brief

Using includes/Core/Util/Debug_Data.php,
- Update the get_fields method to include the verification_status key to $fields array. The value should be a new private method get_verification_status_field.
- get_verification_status_field should return an array with the keys below with their respective values as per the AC.
  - label
  - value
  - debug
- To check whether the user is verified, use the Authentication class which is already instantiated in the Debug_Data class with the following options:
  - To check if user is verified: $this->authentication->verification()->get();
  - For file verification: $this->authentication->verification_file()->get();
  - For meta verification: $this->authentication->verification_meta()->get();

Test Coverage

No new tests to be added.

Visual Regression Changes

QA Brief

Check that the new field “Verification Status” displays the correct values for each option mentioned in the AC

Changelog entry

Add a new “Verification Status” row to the Site Health information for Site Kit.

Issue Analytics

State:
Created 2 years ago
Comments:10 (3 by maintainers)

Top GitHub Comments

1reaction

felixarntzcommented, Jun 28, 2021

@aaemnnosttv I’ve defined ACs here, putting this under “User Status”, since it’s a similar type of value to “Site Status” and “User Status”, plus it’s closely related to the “User Status” value (since e.g. “not-verified” would also indicate a problem here).

We’ve decided to add this enhancement in a support team meeting last week, so moving it forward.

0reactions

wpdarrencommented, Jul 8, 2021

QA Update: Pass ✅

Verified:

When the user is not verified (Site Kit is not activated) then the verification status is not verified

When a HTML tag is manually entered into the <head> of the site then the verification status is Verified outside of Site Kit

When a HTML file is uploaded (or Site Kit creates Search console) then the verification status is `Verified through file

When a Meta tag is used then the verification status is Verified through meta tag

Top Results From Across the Web

HIPAA Verification Guidelines: How to Verify a Request for PHI

The HIPAA Privacy Rule requires you to verify the identity and authority of anyone requesting PHI. This blog provides guidelines on how to...

Authentication of Patients and Participants in Health ... - NCBI

Authentication is an essential step for obtaining consent through online methods or health information exchange as mentioned in the previous ...

Technical Safeguards - HIPAA Security Series #4 - HHS.gov

“Implement procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed.” In general, ...

Evaluation of Health Information on the Web - LibGuides

Links should be included so that users can verify content on the site and they should lead users to other reliable sources of...

Verifying your identity in the Marketplace

Without this verification process, someone you didn't authorize or give permission to could create an account and apply for health coverage in your...