null/Queue-North-Website
null
/
Queue-North-Website
1
0
Fork 0
Code Issues 27 Pull Requests Packages Projects Releases Wiki Activity

Bug: 25+ years claim is unverified (not on original site) #110

New Issue
Open
opened 2026-05-17 21:18:51 -05:00 by null · 0 comments
null commented 2026-05-17 21:18:51 -05:00
Owner
Copy Link

Problem

Multiple pages reference 25+ years of experience, but this claim does not appear on the original queuenorth.com site. The original site says no specific number of years.

Affected locations:

  • Home.jsx meta description (line 66): 25+ years of proven reliability
  • Home.jsx hero text (line 85): 25+ years of proven reliability
  • Home.jsx JSON-LD (not checked but likely)
  • About.jsx meta description (line 9): 25+ years of experience
  • About.jsx meta og:description (line 11): 25+ years of experience
  • Contact.jsx list item (line 186): 25+ years of industry experience
  • Footer.jsx bottom bar: 25+ Years Experience

This is similar to the Houghton, MI issue we already fixed - an unverified claim.

Decision needed

  • If 25+ years is accurate and owner-confirmed, keep it
  • If not verified, remove or change to a vaguer claim like proven experience

Severity

Medium - unverified claims on a business site can damage credibility

## Problem Multiple pages reference 25+ years of experience, but this claim does not appear on the original queuenorth.com site. The original site says no specific number of years. Affected locations: - Home.jsx meta description (line 66): 25+ years of proven reliability - Home.jsx hero text (line 85): 25+ years of proven reliability - Home.jsx JSON-LD (not checked but likely) - About.jsx meta description (line 9): 25+ years of experience - About.jsx meta og:description (line 11): 25+ years of experience - Contact.jsx list item (line 186): 25+ years of industry experience - Footer.jsx bottom bar: 25+ Years Experience This is similar to the Houghton, MI issue we already fixed - an unverified claim. ## Decision needed - If 25+ years is accurate and owner-confirmed, keep it - If not verified, remove or change to a vaguer claim like proven experience ## Severity Medium - unverified claims on a business site can damage credibility
null added the
content
data-integrity
owner
owner-input
 labels 2026-05-18 09:30:06 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
dev
main
v0.8.0
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels   
P0 Critical

Critical — must fix before production. Data loss, security, or outage risk.

  
P1 High

High — should fix soon. Functional bugs, security hardening, data integrity.

  
P2 Medium

Medium — fix in next cycle. Quality of life, robustness, minor security.

  
P3 Low

Low — nice to have. Polish, optimization, minor UX.

  
accessibility

Accessibility issues

  
backend

Server-side code, API, database.

  
bug

Something is broken or behaves incorrectly.

  
content

   
data-integrity

Data consistency, constraints, validation.

  
enhancement

Feature or improvement request

  
frontend

Client-side code, UI components.

  
infra

Docker, deployment, CI/CD, infrastructure.

  
integration

   
owner

Direct feedback from the site owner. Top priority.

  
owner-input

   
performance

Performance or optimization.

  
performance

   
phase-7

   
phase-8

Phase 8 — Deferred enhancements (testimonials, blog, SEO, performance)

  
security

Security vulnerability or hardening.

  
seo

   
ui

UI/visual issues

  
ux

User experience issue.

No Label
P0 Critical
P1 High
P2 Medium
P3 Low
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
performance
phase-7
phase-8
security
seo
ui
ux
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: null/Queue-North-Website#110
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?