Visual Identity — logo, colours, fonts.
How ScoutRival reads your palette off your site, why it sometimes hands you our orange instead of yours, and the ten-second fix.
Your logo, three colours and two fonts. This is the tab people ignore — and then wonder why every generated image looks like ScoutRival instead of like them.
What's on the tab
- Logo — upload or replace. 5 MB max, and it must be a PNG, JPG, WEBP or SVG.
- Primary, secondary and tertiary colour — three hex values, with a picker.
- Heading font and body font — with autosuggest.
- Live preview — on the right, updating as you type, so you can see the kit rather than imagine it.
The primary button is Save & Continue, which saves and moves you on to Voice.
The logo
We try hard to find the real one: we look for an image in your header or nav with "logo" in its alt text, its class, or its filename, and failing that, the image inside your home link. If none of that matches, we fall back to a logo CDN, then to a plain favicon.
On a lot of small-business sites, none of those patterns match — and the fallback we land on is your favicon, at 128 pixels wide. It's the right image but the wrong resolution, so it looks soft in the preview and worse in anything generated from it. The fix takes ten seconds: hit Replace logo and upload the real file.
“My colours are ScoutRival orange”
If your palette reads #FB7B3D · #1E293B · #BEF264 — a warm orange, a dark navy and a lime — those are our brand colours, not yours. It means the extraction found nothing usable and the form fell back to its defaults.
It happens when there's no logo to count pixels from, when the logo we found is a monochrome favicon, or when the site is one big background image with no readable colour signal.
Upload a proper logo, then hit Re-extract. If that still doesn't land it, just type the three hex codes in yourself — the fields are ordinary inputs, and a value you typed is never overwritten by a later AI pass.
How the palette is actually read
It's worth knowing what the pipeline does, because it explains what it can and can't get right. Three layers, in order:
Read your HTML
Fonts come from your Google Fonts links and your inline CSS rules — a heading rule gives us the heading font, a body rule gives us the body font. The favicon comes from your icon tags, or a probe for /favicon.ico. We also pick up your theme-colour tag if you have one.
Count the pixels in your logo
We extract the actual colour swatches from the logo and the favicon, and rank them — favouring vivid, distinctive colours over the near-white and near-black that come from page backgrounds. The top three become your palette. This is deterministic: no model is guessing.
Ask AI to pick — only if the first two fail
If the logo produces fewer than three usable swatches, or they're all muddy greys, an AI vision pass runs. Crucially it is asked to pick from the candidate list we already extracted, not to invent hex codes. That constraint exists because inventing is exactly what the old version did — and why "every brand comes back ScoutRival orange" was a bug we had to fix.
If all three layers come up empty, your theme-colour tag is used as a single seed. If there isn't one either, you get the defaults — see above.
The confidence hints
Each colour and font field can carry a small chip underneath it. They mean:
- No chip — either we're confident, or you set the value yourself. Nothing to do.
- Amber: "Detected · confirm" — we got it from a middling signal. Glance at it; it's probably close but might not be exact.
- Red: "Couldn't lock down — pick manually" — we're telling you honestly that we guessed. Type the right value in.
We deliberately stay silent when the extraction was strong. A chip on every field would just be noise.
Re-extract is safe here
The Re-extract button on this tab re-runs the read against your website and merges the result: a field is only overwritten if the new run actually found something for it. Anything you set by hand and anything the run couldn't improve on is left alone. Press it as often as you like.
The Re-extract on the onboarding Confirm screen is a different thing entirely — it wipes your identity and your setup progress before re-running. This one, on the Identity tab, never blanks a field. The full difference →
If the re-extract runs but finds nothing new, it says so rather than pretending: "Re-fetched the site but couldn't pull any new colors or fonts." That's your cue to upload a clearer logo or set the values by hand.
Where your brand kit is used
Colours and fonts don't change a single word ScoutRival writes. They change everything it draws:
- Compose images and Prompt Studio — your palette and fonts are written into the image brief, so generated graphics come out on-brand instead of on-stock
- BlogCraft thumbnails and infographics — same
- Exported BlogCraft articles — the standalone HTML export is styled with your primary colour and heading font
- The live preview on this tab, so you can check it before you commit
Which is the honest reason to fix this tab: if your images look generic, this is the field to look at — not your voice, and not your services.