Aria works best when you brief it the way you would brief a teammate. The patterns below are what we have seen produce the best results.
Click before you prompt
The fastest way to point Aria at the right thing is to click on it first. If you have a section, container, or block selected when you send your message, Aria treats that as the target.
So when something is selected, these prompts all work cleanly:
"Make this bigger."
"Change the color to our brand teal."
"Rewrite this in a warmer tone."
"Move this above the gallery."
No need to describe which section. Aria already knows. This also stops Aria from hunting around your site for a "similar" section on the wrong page.
Use the creation verbs when you mean it
Aria pays attention to your verbs. Saying "add a hero" on a page that already has a hero will pause Aria — it will ask whether you want a second one or to refine the existing one.
If you want a second one, say so:
"Add another hero below this one."
"Create a second testimonials section for repeat guests."
"Add one more card to this grid."
If you want to refine what's already there, lead with that:
"Make this hero punchier."
"Update the gallery captions."
Either way is fine. Being explicit prevents the back-and-forth.
Mention images when you want them
By default, Aria leaves image fields empty when you add new structure. You will see a one-click Generate images button right after the change lands. This is on purpose — it keeps Aria from generating photos you didn't ask for.
If you want images in the same step, name them in your prompt:
"Add a hero with a misty forest photo at golden hour."
"Build a gallery with 5 mountain shots, moody and monochrome."
"Regenerate the about-page photos — softer light, less staged."
You can also limit scope explicitly:
"Only change the images, leave the copy alone."
"Just the 3 card photos — keep the section background as is."
The more specific the prompt, the more useful the result.
Stack edits in one prompt
Aria is good at doing several related things in a single turn. Instead of three separate messages, give it one:
"Change the hero title to 'Mountains, slow.' the subtitle to 'A small portfolio in Truckee.' and the button to 'See our cabins'."
"Update all three card titles and pull the descriptions from our 2024 reviews."
This is faster, and the changes land together so you can review them as one unit.
Name your stuff
Aria reads your portfolio — every property, every amenity, every market. The more you anchor your prompt in those real names, the better the output:
"Write descriptions for our Big Sky properties — emphasize ski-in access."
"Build a landing page for families traveling to our Gulf Coast units."
"Add a section about the Truckee A-frame, focused on the renovation story."
Generic asks like "write descriptions for our cabins" will get you generic copy. Specific anchors get you specific copy.
Brief the voice you want
Aria has a built-in preference against vacation-rental brochure speak. It tries to avoid words like sophisticated, refined, nestled, sanctuary, oasis, bespoke, indulge, rejuvenate. But the more direction you give, the better Aria can deliver:
"Operator voice, not a resort brochure. Short sentences."
"Down-to-earth, no-bullshit, talk to the guest like a real person."
"Match the tone of our existing About page — restrained, specific, not folksy."
"Lean into the family-trip emotion. Specific details, not generic praise."
When you give Aria voice direction, it is treated as a hard constraint, not a suggestion. Aria will hold the line on the rest of the page.
Lean on your Sightline Report
If you have generated a Sightline Report (and on launch, you can generate one from your dashboard), Aria reads from it any time you ask for branded copy — headlines, taglines, property descriptions, blog topics, SEO meta, hero text.
That means for any copy-heavy prompt, you can lean into the report rather than re-explaining your brand:
"Write a new homepage hero using our positioning statement."
"Draft three blog topics from the priority list in our Sightline Report."
"Rewrite the property descriptions using the voice attributes Sightline pulled from our reviews."
You don't have to quote it — Aria pulls the relevant section automatically. But naming it in the prompt nudges Aria to lean on it harder.
Give Aria real facts
Aria will not make up review counts, star ratings, awards, years in business, or guest counts. If a claim like that matters to your page, tell Aria the actual number:
"Add a stats row: '4.9 average rating across 480 verified stays since 2019.'"
"Mention that we won the Truckee Chamber Small Business award in 2024."
If you don't give Aria the facts, it will either leave those fields blank or write around them. Both are better than fabricated numbers on your live site.
When Aria gets it wrong, just tell it
The fastest way to course-correct is plain feedback in the next message:
"I don't see that change." → Aria re-reads the page and verifies.
"This is too luxury, more lived-in." → Aria rewrites with the new direction.
"That landed on the wrong section." → Aria looks again, finds the right one, fixes it.
"Skip the testimonials — we don't have them yet." → Aria removes the section.
Aria will not double down on a claim you contradict. It re-checks and adjusts.
Quick patterns that work
When you want to | The shape of the prompt that works best |
Tweak something visible on screen | Click it first, then say "make this..." |
Add a second copy of something | Use "another", "a second", or "one more" |
Change copy and structure together | Stack it in one prompt |
Get images alongside structure | Name the visual you want |
Skip images for now | Just describe the structure; click Generate images later if you want them |
Match your real brand | Name the properties, markets, voice attributes you want pulled in |
Use a stat or claim | Give Aria the actual number |
Iterate on tone | Tell Aria what was off ("too luxe", "too folksy", "too generic") |
A note on what Aria does not touch
Aria works inside the site editor. It does not publish your site, change your domain, edit your booking engine, change pricing, or touch your PMS sync. Those stay in your hands.
If you ever ask Aria for something outside the editor and it tells you it can't help, that's why. Reply to your CraftedStays onboarding thread or message us in Intercom and we will point you to the right place.
For the basics on prompting Aria, see How Aria builds your site. For the strategic playbook Aria reads from, see Your Sightline Report.