Visibility / Evidence
All 25 criteria from the original brief, with implementation notes, evidence and next steps. External search and AI outcomes remain pending until observed.
Static HTML, unique page metadata, canonical URLs, reciprocal hreflang, sitemap, crawl directives and local assets are implemented. Public hosting access and Search Console indexation require external verification.
Verify public access and ownership in Search Console; inspect both language URLs and submit the sitemap.
One descriptive H1 per page, semantic sections, clear headings, role and technology terms, contact links and native HTML content. Descriptions and titles are localized.
Review query relevance with actual search impressions after indexing.
The profile connects enterprise engineering with agile leadership: Azure, Terraform, AKS and .NET alongside Scrum, Product Ownership and OKRs. Work summaries and a Scrum presentation provide experience-based content; external authority is not established by this build.
Publish specific technical case studies and link the strongest relevant articles to the profile.
ProfilePage and Person JSON-LD use one persistent Person identifier across languages. Name, role, description, location and personal sameAs links match visible content.
Keep names, employment dates and descriptions aligned across personal profiles.
Official profile links are present. Outbound links do not establish independent backlinks, endorsements or third-party attribution.
Document authentic inbound references and attributable contributions; do not manufacture mentions.
Direct, factual answers are available in the FAQ. Google chooses whether to show a featured snippet; none has been observed for this new site.
Record a dated query, locale and screenshot or source URL if a snippet appears.
Six questions explain the combined focus, agile leadership, Enterprise Grade engineering, compliance scope, software development and contact. Answers are visible without requiring JavaScript.
Revise questions using real recruiter feedback and search queries.
Natural-language questions and accessible text support conversational discovery. No voice-search placement or separate voice ranking has been measured.
Test realistic queries on chosen services and record outcomes without claiming universal compatibility.
Relevant FAQ content is implemented for visitors. Google retired FAQ rich results in May 2026; FAQPage markup is not used to promise that display.
Keep answers concise, factual and current. FAQ rich-result eligibility is not applicable.
Readable HTML, factual answers, visible evidence and entity consistency follow SEO fundamentals. Eligibility and appearance in Google AI Overviews still require external checks.
Verify indexation and current generative-search settings in Search Console; record observed citations.
No AI citation has been independently observed. Structured data or a crawlable page is preparation, not proof of a citation.
Record the engine, query, date, cited URL and captured answer when observed.
The site presents consistent textual identity and experience. Visibility in individual LLM products has not been measured; access and behavior differ by service.
Run a repeatable query set in selected services and separate mentions from linked citations.
Personal identity and the NotJustBI author/channel relationship are distinguished. External mentions are not inferred from social links.
Collect genuine third-party mentions of Edgardo and verify they identify the same person.
A single Person entity links LinkedIn, GitHub, Instagram, the NotJustBI author page and Credly. Current certifications link to their public credential records. The brand channel is linked visibly without being declared identical to the person.
Confirm the channel attribution and add independent identity references when available.
No recommendation by an AI service is claimed. Recommendation depends on the question, platform, evidence and current retrieval.
Document genuine recommendations with their context; track separately from simple name mentions.
Both language versions are available as static pages. Google AI Search visibility and other engine inclusion have not been confirmed.
Verify external eligibility and measure impressions after publication.
Engineering, product ownership, Scrum and OKR responsibilities are grounded in the supplied career material. Enterprise Grade describes specified controls, and SBS work is presented as regulated project experience. The video is a presentation, not an independent endorsement; metrics remain qualified.
Add original technical evidence and review claims as experience changes.
This is an external appearance outcome, overlapping AEO AI Overview Optimization. No appearance is marked complete.
Reuse observed evidence from the AEO criterion rather than count the same result twice.
SEO fundamentals and clear, experience-based content are implemented. No separate magic schema or LLMS.txt requirement is assumed for Google.
Check current AI Mode eligibility and record relevant appearances when they occur.
No analytics account or Search Console property is connected. This checklist is an evidence snapshot, not a live traffic dashboard.
Verify ownership, configure available generative-search reporting and add attributable referral/conversion measurements.
The first screen identifies the person, target engineering focus and location, with direct CV and contact actions. Experience comes before the consulting offer.
Validate relevance with recruiter feedback and real queries.
Mobile-first layout, touch-friendly controls, semantic landmarks, keyboard focus, reduced-motion support and both themes are implemented. Field Core Web Vitals and a full accessibility audit are pending.
Review on actual phones and desktops; run performance/accessibility audits and collect field data when available.
Recruiters can download a localized CV, open LinkedIn or start an email. Those actions work as links; clicks do not prove an application, sent email or client acquisition.
Define meaningful outcomes such as qualified inquiries and measure them with consent-appropriate tools.
Engineering and agile leadership have equal prominence, with three capabilities and two case examples each. The timeline, six FAQs, click-to-play Scrum presentation and two-page CVs are available in both languages; CV text is selectable.
Keep translations and downloadable CVs synchronized with the source profile.
Useful work summaries and links to professional content are present. Return visits, reading depth and engagement have not been measured.
Measure meaningful reading and follow-up behavior after traffic exists; avoid optimizing time-on-page alone.
Engineering and agile leadership have equal prominence: three capabilities and two project examples for each. Enterprise Grade refers to documented engineering controls; SBS-related experience is a regulated project context. Neither implies certified compliance or independently measured scale.
Open positioning evidenceThe Scrum video is evidence of a public presentation. It is hosted on the personal NotJustBI channel and is not counted as an independent endorsement or backlink.
Open contribution record · Introduction to Scrum9 certifications and 4 additional badges, each linked to its public Credly record. Expiry status is evaluated against this review date.
Open credential evidence · CertificationsThe site establishes a consistent professional identity. Google decides whether a panel is generated; ownership verification is possible only after a claimable panel exists. No panel is claimed or guaranteed.
Next: verify indexation, collect independent identity references, then check for an attributable, claimable panel.
Google: Knowledge PanelsStatic readable content, dated roles, engineering and agile leadership competencies, and English/Spanish CVs are present. No universal ATS registration or compatibility is claimed.
Download CVProfile data, translated content, theme and checklist definitions are separate from the page generator. Another profile needs its own identity, evidence and outcomes.
Evidence snapshot
This release has a structural verification report. The unchanged CVs retain their page-by-page review from release 1.2. The Chromium report is a historical baseline for release 1.1, not a browser review of this revision. Indexation, field performance and a full accessibility audit remain pending.
The checklist links to official Google guidance supporting each criterion.