Framer and marketing agency
The work page is the one prospects want and the one you cannot index
An agency site here has two features nothing else in this family has. The page prospects most want to read is the page most likely to be locked or covered by an agreement, and the same custom code field exists in every client project the studio has ever built, which makes the key easy to paste in the wrong place.
Why this pairing is its own job
The Framer install guide covers the tag, and the marketing agency guide covers what the assistant has to know. What follows is the part that belongs to neither.
- The work page carries the material that converts and the material you are least free to repeat. Case studies sit under confidentiality terms that often outlast the engagement and sometimes cover the existence of the relationship, so what may be shown and what may be indexed are the same question with the same answer.
- Framer offers page level protection, and agencies use it for work that is not public yet. A locked page is not fetched by a crawl, which is correct, but the deck it was made from is sitting on a drive and is very easy to upload instead.
- The studio's own site and every client site it maintains have the same field in the same place. One key pasted across several projects gives you a single assistant answering on several domains from one pile of material.
- Agency copy is built from components and variants, so the deliverables list a prospect is looking for may be assembled at render time rather than written into the page. It is worth knowing which of your service pages actually contain their own words.
What changes about the install here
<script src="https://cdn.askably.xyz/w.js" data-key="pk_live_YOUR_KEY" defer></script>The tag is the same one on the Framer guide. Everything below is about where it goes on a marketing agency site specifically.
One project, one assistant, one allowlist
Before pasting anything into a client project, create a separate assistant for that client with its own key and its own allowlist covering their domain, the www form of it and the staging address. The five minutes that takes is the difference between a clean deployment and a shared one you cannot separate later.
Set the origins deliberately per client rather than accumulating every domain onto one list. An allowlist that grows to cover a studio's whole portfolio has stopped being a control and become a formality, and it is the only thing standing between one client's site and another client's material.
Published custom code on this platform is on a paid site plan, which for client work is a conversation to have before you promise a launch date. A client project on a free plan cannot carry the tag whatever was agreed in the kickoff.
The locked work page, and the deck behind it
Page protection does what you expect: the page is not served without the password, so a crawl does not read it. That covers the site. It does not cover the material, and the material is where agencies leak, because the case study deck with the real numbers in it is the most tempting file on the drive.
Check what you are permitted to publish before anything is uploaded, client by client. Names, figures, the sector, and in some agreements the fact of the relationship at all. An assistant that helpfully describes an unpublished engagement has not made a good impression, it has breached a term.
Index the approved wording rather than the internal version, and let the assistant quote it. Performance claims in particular were written with a qualification next to them, and a summary is exactly where the qualification goes missing.
Check which pages contain their own words
Open the live service pages and search for a phrase you know is on them. Agency sites lean on components, variants and scroll driven sections, and the copy a prospect reads is not always in the document a crawl receives. The pages most likely to fail this test are the designed ones, which is to say the ones you are proudest of.
Where a page comes back thin, the fix is not to redesign it. Publish a plain page with the same content, the deliverables and the engagement terms written as text, and index that one. Prospects who want the designed story will read the designed story. The assistant needs a version it can quote.
Where the answerable material lives
| Deliverables written as page text | What a retainer, a build or a paid media programme actually produces: the artefacts, the cadence, the reporting. Written on a page rather than assembled from components, because this is the material that qualifies a prospect and it has to be readable to do that. |
|---|---|
| Case studies, in the approved wording only | The published version, quoted rather than summarised, with the qualification that sat next to the number still attached. Anything you would not want repeated verbatim in front of the client concerned does not go in. |
| The commercial terms page nobody links to | Asset and intellectual property ownership at the end of an engagement, who holds the ad accounts and analytics properties, notice periods, and whether ad spend is billed through you. Prospects ask late and should ask early, and design led sites almost never have room for it. |
| An explicit list of what stays out | The locked work, the unpublished pitches, the client names under agreement. Worth writing down as a list, because the material is added by whoever is free that week and the reasons a file is off limits are not visible in the file. |
The first thing to get right
Create a separate assistant, key and allowlist for every project before the tag goes into any of them, including the studio's own.
This is the only item here that cannot be corrected cheaply later. Material and conversations that have been mixed across clients cannot be unmixed afterwards, and the separation costs nothing on the day you set it up.
The failure that belongs to this combination
One key across a portfolio
The studio sets up an assistant for its own site, it works, and the next client build reuses the same tag because it is already in the project template. Six months later that key is live on nine domains and the allowlist has been widened each time to keep them all rendering.
The failure that follows is not a technical one. A visitor on one client's site asks a question, and the answer comes back citing a page belonging to a different client, because there is one body of material and it does not know whose site it is standing on. Every one of those replies is a disclosure the studio made on its client's behalf.
The conversation record has the same problem in reverse. Nine clients' enquiries in one list, with no clean way to separate them and no way to hand a client their own. Separate assistants from the start, and keep a written note of which project carries which key.
Before you go live
- The origin the page is served from has to be on the allowlist for that assistant, or nothing renders and the browser console says which origin was refused. An apex domain and its www are two different origins to a browser, so list both, along with any staging or preview host you want it to work on.
- Open the site as a visitor would, on the pages a marketing agency visitor actually lands on, and ask it something only your own material could answer. A widget that renders is not the same as a widget that has read anything.
Questions
- Can we run one assistant across all the sites we build?
- You can, and it is the mistake this page exists to warn about. One assistant has one set of material, so a visitor on one client's site can be answered from another client's pages. Separate keys per project cost nothing to set up and are impossible to retrofit once conversations and material have been mixed.
- Our best case studies are under NDA. Can it use them if the page is locked?
- The lock stops a crawl reading the page, which is real protection. It has no effect on what you upload, and the deck those case studies came from is the file most likely to be uploaded by somebody trying to be helpful. Keep a written list of what is off limits, because the reason a file cannot be used is not visible in the file itself.
- Should it give a price?
- It should give exactly what you published and no more: the indicative starting point per service, the statement that the figure follows a scope, and the offer of a discovery call. That is a stronger commercial position than either silence or a guess, and it filters the enquiries that were never the right size before they take up a call.
Keep reading
- Installing on FramerFramer keeps custom code in site settings. Paste the tag in the end of body field, publish again, and allowlist the staging address too.
- Everything for a marketing agencyService definitions and engagement terms convert. A price quoted for work nobody has scoped is the trap on an agency site.
- Publishing a financial promotion with a single buttonThe number sits in one element and the sentence that qualifies it in another, and publishing a financial promotion here is one button anyone with access holds.
- A marketing agency on Squarespace, where the work is images and the answers are notAn agency site is mostly pictures. If the case study text sits inside the image, a crawl finds a client name and a caption, and nothing to answer with.
- An agency running a Ghost publication, where the good material is the gated materialThe posts the agency is known for sit behind the members gate, so a crawl gets teasers. What is left to answer from is the commercial detail nobody wrote down.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.