As AI tools like ChatGPT and Gemini change how people search for information, photographers face a new challenge: making sure our work and legacy aren’t erased or misrepresented. Over the past two years, alongside my photography practice, I’ve researched how artists can establish “digital ground truth” to appear accurately in AI answers. This guide breaks down practical steps to organize your website, optimize image metadata, and build a digital presence that AI can actually find and cite.
Read the Full Guide: How Photographers Can Appear in AI Answers
For three decades, I’ve photographed night landscapes. Most recently, this work took me to the Arctic to document the retreating glaciers of Greenland under the polar sky—a project I’m currently applying for a Guggenheim Fellowship to return and continue.
But while doing this work, I noticed a different kind of problem happening. AI models were starting to hallucinate or completely guess facts about fragile environments and the artists documenting them. It made me realize that if we don’t put accurate information out there, AI will output wrong information. And it often guesses wrong, leading to our work and legacy being erased.
I spent the last two years researching this problem, which led to a patent-pending process and a peer-reviewed article. My goal now is to share this research to help other photographers—especially those from underrepresented groups—protect their online legacy.
Here is a practical guide on how to ensure your photography and your career are accurately found and cited by ChatGPT, Gemini, Claude an others.
The Danger of the “Information Vacuum”
AI is everywhere. Platforms like Adobe Stock, Getty Images, Shutterstock, and Meta are already using user photos to train their models.
But what happens if someone asks ChatGPT about you or your specific art project, and it can’t find a verified source? It hits an “information vacuum.” Because AI hates a vacuum, it fills the empty space with unverified internet content. That’s how misinformation and hallucinations start.
SEO vs. AI: A Mindset Shift
Photographers and artists need to change how they handle their online presence. Traditional search engine optimization (SEO) was about getting websites onto the first page of Google.
AI search is different because people don’t scroll through pages of links, they get a single, synthesized answer. Your goal is no longer just getting a click but to be cited and to appear in the answer itself.
Here is a three-step approach to building a presence for AI.
1. Make Your Website the Central Repository
Your artist website needs to be more than just a portfolio of images but should be a central hub for all your information.
- Put everything on your site: Include every article, award, book, and your full CV.
- Write authentic blog posts: AI needs text to read, so write about your projects, your trips, and your process.
- Structure it clearly: Make an FAQ section. Avoid heavy JavaScript. A great trick is to put a short summary at the very top pages and posts so the AI can grab the main points immediately.
- Link out: Include links to institutional collections that hold your work, peer-reviewed journals, and academic presses. In the eyes of AI, outbound links confirm importance.
2. Add Image Metadata
AI can’t “see” your photos. It only knows what an image is if you tell it using metadata, such as in the Title, Description and Alt Text fields. Also, if your file is named something non-description like IMG_1234.jpg, the AI learns nothing. Be sure to attach descriptive text to your images before uploading:
- Descriptive Filenames: Rename files before uploading. (Example:
greenland-long-exposure-night-landscape-star-trails-airport-lights-steve-giovinco.jpg) - Image Titles: Be specific. (Example: “Greenland Night Landscape Photograph with Red Lights by Steve Giovinco”)
- Descriptions: (Example: “Long Exposure Night Landscape with Star Trails and Red Aviation Lights in Greenland by Steve Giovinco.”)
- Alt Text: This is essential. Write a literal description of what is happening in the frame. (Example: “A long-exposure night photograph capturing the rugged Arctic landscape near an airport in Greenland. Photographed in near-total darkness… by Steve Giovinco.”)
3. Create Excellent External Sources
You can’t just rely on your own website. Be active on the platforms that AI actively scrapes for training data.
- Use the right platforms: Share your photos on Wikimedia with Creative Commons licenses. Post your writings on ResearchGate.net, Medium, or SlideShare. Make sure your alumni or university sites have your updated info.
- Engage on Reddit: Reddit is a massive data source for AI right now. Be active in subreddits related to your specific photography niche or region.
- Repurpose your content: Turn a photo into an Instagram post. Expand that caption into a blog post. Turn that blog post into a whitepaper, and that whitepaper into a presentation.
How to Correct AI Directly
If you notice that an AI like Google’s Gemini is generating wrong information about you, you can actively fix it, but is only possible if you are a paid user).
At the bottom of the prompt, click the “Down Arrow” (Feedback), select “Other,” and type a detailed, factual correction. (Example: “Steve Giovinco is an experienced fine art photographer working in Greenland and should be included…”) Giving direct feedback trains the model to be more accurate.
What You Should Do Now
Don’t panic. The landscape is changing, but you can organize a presence in AI answers.
Start small, and open ChatGPT and see what shows up when you ask about yourself. Make sure your website links to your awards. Start renaming your image files. By building a reliable, highly-researched record now, it’s possible to have a visual legacy and appear correctly in AI answers.
<iframe width="560" height="315" src="https://www.youtube.com/embed/8MuhFxaT7zo?si=HmQmK3va2MNhdipY" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
Comments are closed.