Relying on Third-Party Listings to Explain the Food Truck
Evidence: A directory, marketplace, or social profile gives customers a clearer view of the menu, catering offer, current schedule, ordering route, or event details than the truck's own website. The source previously cited 15-30% commissions for third-party platforms; because no supporting source URL appears in this JSON, treat that range as historical context requiring source reconciliation rather than a verified current benchmark.
Consequence: Customers may depend on information the operator does not fully control, while the truck's own result provides less useful context for branded, local, ordering, and catering searches.
Correction: Strengthen the site around real decisions such as menu review, ordering, catering, private events, and genuine operating locations. Do not create a separate location page merely because an area is named in a service radius; a location page should represent a real location and contain useful location-specific information.
Owner: Marketing or the site owner, with operations confirming what the truck actually offers and where it serves.
Verification: Compare the truck's pages with the third-party results customers are likely to encounter. Confirm that important business, service, and ordering information is current, indexable, internally linked, and easier to verify on the owned site.
Severity: critical
Publishing Location Details That Conflict With the Real Schedule
Evidence: The website, event pages, social channels, directory listings, or Google Business Profile disagree about hours, stops, service areas, or availability. A second warning sign is broad city copy that never tells a customer where the truck is actually expected to serve.
Consequence: People can travel to the wrong place, abandon a visit, or stop trusting other operating information. Search systems also receive inconsistent context about the business and its locations.
Correction: Maintain one operational source of truth for the schedule, then update the website and eligible customer-facing profiles from that source. Do not present posting frequency, real-time updates, or any single profile action as a guaranteed local ranking mechanism.
Owner: Operations owns schedule accuracy; marketing or the site team owns publication and profile consistency.
Verification: Compare the live website and important profiles with the actual route, event, or service schedule, then test the mobile journey a customer would use shortly before visiting.
Severity: high
Allowing Mobile Friction to Interrupt Orders and Catering Inquiries
Evidence: The homepage may feel usable while the menu, ordering provider, map, contact form, or catering inquiry becomes slow, unstable, or difficult to complete on a phone. The source previously connected load times above 3 seconds with a 40-50% drop-off and included a 60% example; because no supporting source URL is present, treat those figures as historical claims requiring reconciliation rather than universal thresholds.
Consequence: A visitor with clear intent may leave before checking the location, placing an order, calling, or submitting a catering request. Conversion friction and organic visibility should be diagnosed separately instead of assuming one directly causes the other.
Correction: Reduce unnecessary scripts, oversized images, layout movement, redirect chains, and avoidable third-party dependencies across the complete mobile path, including any external ordering or booking step.
Owner: The developer or technical site owner, with the ordering or booking provider involved when the failure sits outside the primary website.
Verification: Test the real customer journey on representative phones and connections, review Core Web Vitals when enough field data exists, and confirm that order and inquiry interactions finish without layout or input failures.
Severity: critical
Using Structured Data Instead of Fixing the Underlying Page
Evidence: Markup contains menu, event, local, or business information that is stale, absent, inconsistent, or invisible on the page. Another sign is a generic schema type added by default even when it does not accurately describe the page or entity.
Consequence: Search systems receive conflicting signals, while the team spends time maintaining markup that does not solve the customer's information problem.
Correction: Keep structured data accurate, eligible, and aligned with visible content. Use an appropriate supported type where it fits, but do not promise a rich result, local ranking improvement, or other search outcome from markup alone.
Owner: SEO or development, with operations confirming the underlying business information.
Verification: Validate the implementation, compare marked values with visible page content, and review relevant Search Console reports for structured-data issues.
Severity: high
Writing Generic Hospitality Copy Instead of Food Truck Decision Content
Evidence: The site uses broad lifestyle language but does not answer practical questions about cuisine, menu availability, dietary information where applicable, catering scope, event types, ordering, pickup, or where the truck currently operates. An older source example used 5 itinerary ideas, which is not a useful content model for a mobile food business.
Consequence: Pages may attract weakly matched visits or fail to support the searches that occur before someone chooses a stop, places an order, or requests catering.
Correction: Build content around real customer decisions and maintained operating facts. Use menu context, images, event information, and service descriptions only when the business can keep them accurate.
Owner: Content or marketing, with menu, service, and operating claims reviewed by operations.
Verification: Check query data and landing-page behavior for relevant food truck, menu, event, catering, and local intent instead of relying on unrelated informational traffic as evidence of success.
Severity: medium
Neglecting Image Context and Conversational Search Basics
Evidence: Key food or truck images have vague file names, missing or misleading alt text, oversized files, or too little surrounding context. The source used 'IMG_1234.jpg' as an example of poor labeling, but renaming a file should not be presented as a guarantee of image visibility.
Consequence: Users and search systems receive less context about important visual content, and heavy image pages can become slower than necessary.
Correction: Use descriptive file names and accurate alt text where appropriate, compress images, and place them inside useful page context. Answer recurring customer questions in plain language, but do not imply that voice assistants or Google AI features require a special FAQ format.
Owner: Content and web teams.
Verification: Inspect representative pages and images, confirm accessibility-oriented alt text matches the image purpose, review image indexation where relevant, and check whether common conversational questions are answered clearly on the page.
Severity: medium
Leaving Business Information Inconsistent Across Customer-Facing Sources
Evidence: The food truck name, phone, website, hours, or operating information differs between the site and important third-party profiles. Mobile businesses create additional confusion when a stable business address, a service area, and a changing event stop are treated as though they mean the same thing.
Consequence: Customers may call an inactive number or rely on outdated stop information, while search systems receive conflicting business data.
Correction: Audit the sources customers actually use, fix material inconsistencies, and document the difference between stable identity information and the truck's changing public schedule.
Owner: Local SEO or marketing, with operations supplying authoritative identity and schedule data.
Verification: Recheck important customer-facing sources after changes and maintain a record of the authoritative values. The source included a historical example involving a #1 Maps position; without a supporting source URL, treat that example as illustrative rather than verified evidence of causation.
Severity: high
