App still not indexed by search enginges and Streamlit image not updated

Community Cloud
1

So, it has been well over a week since I created my app, and well over a week (eleven days) since I set the site’s metadata using st.set_page_config(). I previously posted that there were issues with my site showing up in Streamlit Community Cloud’s internal search, but while that particular issue seemed to have been resolved, there are clearly still problems, and I would really appreciate a Streamlit person helping me to investigate them:

  1. The app’s share preview has not changed since it was first generated seven days ago, even though there have been multiple site updates since then.
  2. I’m pretty certain that what successfully caused Streamlit to generate the share preview and for my site to appear in the Streamlit Community Cloud search in the first place is my accidentally clicking ‘edit with GitHub Codespaces’, since I’ve tried ‘clear caches’ multiple times to no avail. There should not be a connection between those two.
  3. The site has still not been indexed by Google or Bing, even though this is supposed to happen on a weekly basis.
  4. The ‘deploy’ link is still showing at the top of my page, as per my previous post, although this isn’t a real problem for me – but if the AI’s response last time was correct, that shouldn’t in fact be the case.

My site’s URL is https://latin-morph.streamlit.app/

Thanks in advance for any help!

2

Welcome back to the community and thanks for your detailed follow-up! :blush: You’re right that public Streamlit Community Cloud apps are supposed to be indexed by search engines weekly, and share previews (title, description, screenshot) are updated daily. However, there can be delays—especially for search indexing, which sometimes takes up to two weeks even after all metadata is set via st.set_page_config and the README is updated. The share preview image may also take up to 24 hours to refresh after changes, but persistent issues beyond that could indicate a caching or backend delay. According to the docs, using “Edit with GitHub Codespaces” shouldn’t directly affect indexing or share preview generation, so that may have been coincidental. Clearing the cache from the app menu only affects your app’s data cache, not the share preview or search index status. The “Deploy” link showing up is likely a UI caching glitch and should disappear after a full refresh or once the app is fully recognized as deployed, but it’s not functionally problematic.

For your specific issues:

  • Search engine indexing: It can take several days to two weeks for Google/Bing to index new or updated public apps, even if everything is set up correctly. Make sure your app is public, has a descriptive title via st.set_page_config(page_title=“…”), and a good README description. You can check index status by searching site:latin-morph.streamlit.app on Google. If it’s still not indexed after two weeks, try rebooting your app from the dashboard and double-checking your repo’s README and app settings.
  • Share preview: The preview image is generated by a daily screenshot, so it may take up to 24 hours to update after deployment or changes. If it hasn’t updated after several days, this could be a backend delay—there’s no user-facing control to force a refresh.
  • “Deploy” link: This is not standard for public apps and may indicate a UI caching issue or a temporary glitch; it should resolve itself, but you can try a hard refresh or different browser.

For more details, see the official docs on SEO and search indexability and share previews. If the issue persists after two weeks, consider reaching out on the forums with your repo and code for deeper investigation. Community members, feel free to jump in if you’ve seen similar quirks or have tips for speeding up indexation!

Sources:

3

I did a full reboot (not for the first time!) two days ago at 20:02:11 UTC. It (finally) fixed the ‘deploy’ link issue, but as of 12:34:17 UTC today the sharing preview (on Streamlit itself, not as already shared elsewhere) has still not updated. If there’s a backend delay, surely that needs to be addressed somehow?

I have my title set with st.set_page_config, I have a substantial README on GitHub. The site was even shared on social media over 2 weeks ago. I’m unsure what’s preventing the search engines from finding it, although hopefully solving the glitch with the deploy link will cause that to solve itself within another week. If it does not, is there anyone I can contact for assistance?