Brandcore.io Mariscos Costa AlegreCosta Alegre
The Table
01 / 09
BRANDCORE.IO×MARISCOS COSTA ALEGRE
Mariscos Costa Alegre Restaurant & Bar

Private website & growth proposal · 31 October 2026

A coastal table.
A stronger welcome.

Family recipes, three San Jose locations and a patio that fills on a weekend. A proposed website that makes the menu, the locations and the phone number easy to find.

  • 3San Jose locations
  • 2018family-run since
  • Cold bar to sushione kitchen, one menu

Luis GuzmanPrepared by Luis Guzman
Client Success · Brandcore

THE ACTUAL COSTA ALEGRE MARK, AS A LIT COASTAL SIGNMove the pointer. Press Next.

02 / Website audit · public pages checked 31 October 2026

The food is the draw.
The website is a detour.

Six observable problems on mariscoscostaalegre.com. Not taste — friction a hungry guest meets before the first plate: a menu locked in a Drive file, no hours anywhere, and a phone number two clicks away.

mariscoscostaalegre.com/menu LIVE · 31 OCT 2026
The live Costa Alegre menu page, showing a Google Drive document preview and no readable dish text
THE ENTIRE MENU · ONE EMBEDDED DRIVE FILE The page has no dish names or prices in its own text — only a 20-page PDF preview.
mariscoscostaalegre.com LIVE · HOME
The live Costa Alegre homepage with a full-screen oyster photograph, location count and two ordering buttons
01

The menu is a Drive file.

/menu embeds a Google Drive preview of a 20-page PDF. No dish name appears in the page’s own text; the preview is a third-party embed.

SOURCE · /menu · 1 Drive iframe

03

The homepage has no tap-to-call.

0 tel: links on the homepage. The number appears only after choosing a location and opening its detail page.

SOURCE · homepage · 0 tel: links

04

The locations page withholds the details.

Three names and three “View More” buttons. No address, phone number or hours on the page itself.

SOURCE · /locations · names only

05

Two answers about how many locations.

The site says “3 Beautiful Locations.” The embedded menu says “Visit all 4 of our locations” and lists a Gilroy address. One of them is out of date.

SOURCE · /locations vs menu PDF, page 1

06

10.1 MB before the first plate.

85 requests on the homepage. The console logs a failed Weglot request (403, “project has been deleted”) and two Typekit 500s. The meta description is empty.

SOURCE · homepage · 10,068 KB · 85 requests

02 / 09 · The AuditEvery finding is a public page observation, not a customer comment.

03 / The familia · one name, three neighborhoods

A family recipe book.
Three San Jose tables.

Family-run since 2018. The same familia runs all three San Jose locations, with a menu that moves from the cold bar to the hot kitchen to Mexican sushi.

The Costa Alegre patio, shaded and full of guests at lunch
THE PATIO · PUBLIC PHOTOShade, tables and a room that already works. The website should feel like this.
THREE SAN JOSE LOCATIONSSource

Addresses and numbers verified on the restaurant’s own location pages. Hours are not published on the current site.

03 / 09 · The FamiliaDish names from the published menu. No prices shown.

04 / The guest journey · find · choose · order

From “mariscos near me”
to a seat at the table.

Three decisions every hungry guest makes. Today the site makes each one work harder than it should. This is the path we would clear.

01FindSearch & menu

“Do they have aguachiles?”

Today The menu is a Drive preview. Google can index the page, not the dishes.

A readable menu page gives every dish a name, a category and a photograph — the things a guest and a search engine both need.

What we’d buildMenu pages by category, with dish names and photos approved by the family.
02ChooseThree locations

“Which one is closest?”

Today Names only on /locations; the address and phone are one click deeper.

One location card carries the address, a tap-to-call button, directions, hours and the order link for that kitchen.

What we’d buildCall · Directions · Hours · Order, together for each location.
03OrderPickup & catering

“Can I order for a party?”

Today One “Order Delivery” route, repeated in the header and footer.

Keep the existing order link prominent. Add a catering request with date, headcount and pickup location for your team to answer.

What we’d buildThe current order route, plus a guided party-tray request.

04 / 09 · The GuestOrdering integration stays with the restaurant’s existing provider.

05 / Your new website · working concept

Bring the table
closer to every guest.

A homepage, a readable menu and three location pages built around the real dishes and the real rooms. Try the tabs, the menu filters and the phone view.

  • 01
    A location bar that follows the guest

    Call, directions, hours and the order link stay with the location the guest picks.

  • 02
    A menu Google can read

    Dish names, categories and photographs on the page — not inside a PDF preview.

  • 03
    Catering without phone tag

    Date, headcount and pickup location in one request your team can confirm.

Illustrative concept. Dish names, dish photographs and the storefront image are the restaurant’s own public material; hours are a launch input, not a published schedule.

mariscoscostaalegre.com PROPOSED · ILLUSTRATIVE
Costa AlegreMENU · LOCATIONS · OUR STORY
3 LOCATIONS IN SAN JOSE

World famous
mariscos.

Fresh seafood, family recipes and a table for everyone. Pick a location to call, get directions or order.

Order delivery
The yellow Costa Alegre building and patio under a clear sky, reflected in a puddle, from a public photograph of the restaurant
Choose a location
Family-run since 2018Three San Jose kitchensOrder online

05 / 09 · The WebsiteWorking concept · not a live client site.

06 / Our work · before & after

Same business.
A brand-new first impression.

A Brandcore redesign for United Facilities Group: clearer service copy, a stronger visual identity and a prominent quote request. Shown as design work, without performance claims.

United Facilities Group's previous website
United Facilities Group's website rebuilt by Brandcore
BEFOREAFTER · BRANDCORE
United Facilities GroupDrag the divider, or use the arrow keysPublic website · before & after

06 / 09 · The ProofProject imagery from the Brandcore archive.

07 / Launch roadmap · after scope, access and content approval

Three days to plan. Seven to build.
Sixty to follow through.

A proposed schedule for a focused first launch. Ordering integrations, translations and new photography may add time; we would agree that before the clock starts.

01Days 1–3

Strategy & content

  • A 1-on-1 kickoff with your Brandcore partner
  • The menu, dish photos and location details, agreed together
  • Choose the first location — or all three at once
03Days 11–70

Follow-through

  • Google Business Profile details and fresh photos for each location
  • A simple review request, open to every guest
  • Ongoing updates and direct access to your partner
1dedicated partner from day one
10day target after approvals
60days of review and improvement

07 / 09 · The PlanTargets, not guarantees. Scope confirmed in writing first.

08 / Engagement · how a decision becomes a launch

A small,
clear first engagement.

No open-ended retainer and no access requested today. Start with the menu, the three locations and a working first version. Add the rest when it earns its place.

01

What we’d do first

  1. Workshop One working session on the menu, the rooms and the three locations.
  2. Design Homepage, menu, locations and a catering request.
  3. Build Responsive pages, tested on phones, launched with your approval.
02

What we’d need from you

  1. The menu source Your current file, plus any dish photos you want used.
  2. Hours per location The one fact the current site never publishes.
  3. Ordering link The existing provider stays; we link to it clearly.

Domain and hosting access only at launch, never before.

03

What you’d get

  1. A working site Fast on a phone, readable in a search result.
  2. A launch checklist Every page, link and phone number checked.
  3. A 60-day review A real conversation about what guests use.

Scope and fee confirmed in writing after a scope call.

This deck is a proposal, not an agreement. No price, booking or performance result is implied.

08 / 09 · The StartNo client contact details are collected on this page.

09 / The invitation · a conversation, not a contract

Let’s bring more guests
to Costa Alegre’s table.

Bring the menu, the three locations and the questions. We’ll walk through the proposed pages and agree which improvements would help your guests most.

Luis Guzman, Brandcore client partner
Your Brandcore partner
Luis Guzman
Client Success · Brandcore

A direct line to the person who would run the work — not a handoff.

Brandcore.ioBrandcore.io · San Francisco Bay Area Sales Solutions

09 / 09 · The InvitationMariscos Costa Alegre × Brandcore.io

01 / 09 Scroll to read · at the edge, keep going to change page