01↗
TRUSTED SIGNALS
The product needed to communicate useful publisher signals without pretending to know metrics that cannot be verified from public evidence.
Work / Case Study / 04Web Application
Publisher Due Diligence / Web App
PUBLISHER
CHECK
An evidence-first publisher due diligence platform designed to help guest-post and link buyers inspect publicly observable website signals before making a placement decision.
UI/UX × Developmentpublishercheck.app
ROLEUI/UX Designer + Developer
TYPEDue Diligence / Web Application
STACKNext.js / React / Tailwind
STATUSLive MVP
01 / OverviewEvidence
Evidence
before
assumptions
PublisherCheck is a browser-based due diligence tool for inspecting websites before buying guest posts or link placements.
Instead of presenting an arbitrary SEO score, the product focuses on signals that can actually be observed from publicly accessible pages and technical responses.
The report turns a potentially messy research task into a structured interface containing verified checks, site taxonomy, limitations and human-review guidance.
Visit the live project↗02 / ChallengeThe
The
problem
Publisher research often depends on scattered signals. The challenge was to make those signals understandable without manufacturing certainty.
02↗
EVIDENCE FIRST
Every automated result needed to be connected to observable public evidence instead of becoming another unexplained SEO score.
03↗
COMPLEX DATA
A website inspection can produce many different signals. The challenge was turning those signals into a report that remained easy to scan.
04↗
HUMAN REVIEW
Automated checks cannot replace editorial judgment, so the interface needed to clearly separate machine-verified signals from things a buyer still needs to inspect.
03 / SolutionBuilt around
Built around
evidence
01
Built an evidence-first publisher due diligence workflow.
02
Created a simple URL inspection entry point.
03
Grouped automated checks into a clear status summary.
04
Added observable signals for publishing activity and technical health.
05
Surfaced categories, editorial transparency and author attribution.
06
Clearly separated automated checks from human due diligence.
04 / ProcessFrom
From
question
to report
01↗
DEFINE
Defined the core problem around guest-post and link-placement buyers who need fast, observable signals before making a decision.
02↗
STRUCTURE
Organized the report into an assessment summary, individual checks, site taxonomy, scope boundaries and human review.
03↗
DEVELOP
Built the inspection experience as a responsive web application with a focused input flow and structured report interface.
04↗
REFINE
Refined hierarchy, status cards, evidence presentation and the distinction between verified signals and information that requires human judgment.
05 / InterfaceThe
The
inspection
interface
The interface starts with one simple action: enter a website. Everything after that is structured around readable evidence and clearly labeled signals.
Due Diligence Report
06 / InspectionSee the
See the
signals
The report turns a website inspection into a compact collection of statuses that can be scanned first and investigated deeper when necessary.
01CHECK
ACTIVE
PUBLISHING ACTIVITY
Publicly accessible articles found through the site's available structure.
02CHECK
N/A
AVERAGE OUTBOUND LINKS
The interface avoids inventing a metric when the available evidence cannot support it.
03CHECK
WARNING
TECHNICAL HEALTH
HTTPS and core accessibility signals are surfaced for review.
04CHECK
CLEAR
GUEST POST SIGNALS
Contribution guidelines and commercial language can be inspected.
05CHECK
CHECKED
EDITORIAL TRANSPARENCY
Public transparency pages such as About and Contact can be verified.
06CHECK
MISSING
AUTHOR ATTRIBUTION
Author attribution and timestamps are checked from publicly observable markup.
07 / Site TaxonomyUnderstand
Understand
the
publisher
Public categories and navigation structures can reveal how a publisher organizes its content. PublisherCheck surfaces those declared structures instead of hiding them behind a score.
Site Taxonomy
08 / FeaturesWhat I
What I
built
01Website Inspection
02Evidence-First Checks
03Publishing Activity
04Technical Health
05Guest Post Signals
06Editorial Transparency
07Author Attribution
08Site Categories
09Public Sitemap
10Recent Articles
11Raw Evidence
12Human Due Diligence
13Scope Boundaries
14Sample Report
15Inspector View
16Responsive UI
09 / DevelopmentI built
I built
the
system
PublisherCheck was built as a product rather than simply a visual landing page. The interface needed to support an actual inspection flow and turn returned information into a readable report.
The experience separates automated public-evidence checks from things that require human judgment. That distinction is a core part of the product instead of being hidden in small print.
The result is a focused MVP that makes the limits of automated due diligence visible while still giving the user useful signals to investigate.
My contribution
100%Design + Code + Product Thinking
10 / Human ReviewHumans
Humans
still
decide
Automated crawlers can provide structural signals. Placement decisions still require reading, context and judgment.
01↗
READ ARTICLES
Review recent articles for usefulness, originality and actual editorial value.
02↗
INSPECT LINKS
Look at where surrounding posts point and whether the references feel editorial or commercial.
03↗
CHECK AUDIENCE
Consider comments, social engagement, topic fit and whether the readership matches the intended audience.
11 / OutcomeA clearer
A clearer
due
diligence flow
The final result is a live publisher inspection MVP that turns publicly observable website evidence into a structured report while clearly showing where automated analysis stops.
01
LIVE
Deployed PublisherCheck MVP
02
EVIDENCE
Observable public signals instead of fabricated metrics
03
HUMAN
Automated inspection paired with human review
12 / ReflectionWhat this
What this
project taught me
Good product interfaces do not always need to give users more information. Sometimes the most useful thing is making the limits of the information completely clear.
Designing the report taught me how important hierarchy becomes when a product needs to communicate multiple types of evidence at the same time.
Separating automated checks from human judgment made the product feel more honest and gave the interface a clearer purpose.
Live ProjectCHECK IT
CHECK IT
LIVE
Open PublisherCheck and inspect a website through the actual due-diligence workflow, report interface and evidence sections.
Open PublisherCheck↗Next ProjectSHORTLY
SHORTLY
URL
View project→