{"id":1438,"date":"2026-06-13T13:00:00","date_gmt":"2026-06-13T18:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=1438"},"modified":"2026-03-07T03:49:14","modified_gmt":"2026-03-07T08:49:14","slug":"firebase-app-indexing","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/firebase-app-indexing\/","title":{"rendered":"Firebase App Indexing: What Replaced It and How to Migrate"},"content":{"rendered":"\n

Firebase App Indexing was Google's recommended way to surface Android app content in search results. It was part of the Firebase platform and worked alongside Firebase Dynamic Links to connect web content with in-app destinations. In August 2025, Google shut down Firebase Dynamic Links, and Firebase App Indexing went with it.<\/p>\n\n\n\n

If you relied on Firebase App Indexing, your app content may have lost search visibility. This guide explains what Firebase App Indexing did, what has replaced it, and how to migrate. For the broader Firebase shutdown migration, see Firebase Dynamic Links shutdown<\/a>. For the step-by-step migration, see Firebase Dynamic Links migration guide<\/a>.<\/p>\n\n\n\n

What Firebase App Indexing Did<\/h2>\n\n\n\n

Firebase App Indexing provided two capabilities:<\/p>\n\n\n\n

1. App Indexing API<\/h3>\n\n\n\n

The App Indexing API<\/a> let your app tell Google about content the user viewed. When a user opened a product page in your app, your app called the API to report the view:<\/p>\n\n\n\n

\/\/ Old Firebase App Indexing code\nimport com.google.firebase.appindexing.FirebaseAppIndex\nimport com.google.firebase.appindexing.Indexable\n\nclass ProductActivity : AppCompatActivity() {\n    override fun onStart() {\n        super.onStart()\n\n        val indexable = Indexable.Builder()\n            .setName("Product Name")\n            .setUrl("https:\/\/www.yourapp.com\/products\/123")\n            .build()\n\n        FirebaseAppIndex.getInstance(this).update(indexable)\n    }\n\n    override fun onStop() {\n        super.onStop()\n        FirebaseAppIndex.getInstance(this).remove("https:\/\/www.yourapp.com\/products\/123")\n    }\n}\n<\/code><\/pre>\n\n\n\n
This API reported viewed content to Google, which could then surface it in search results for other users.<\/p>\n\n\n\n
2. Automatic Deep Link Handling<\/h3>\n\n\n\n
Firebase App Indexing integrated with Firebase Dynamic Links to handle incoming deep links from search results. When a user tapped an app result in Google Search, Firebase handled the URL routing:<\/p>\n\n\n\n
\/\/ Old Firebase deep link handling\nFirebaseDynamicLinks.getInstance()\n    .getDynamicLink(intent)\n    .addOnSuccessListener { pendingDynamicLinkData ->\n        val deepLink = pendingDynamicLinkData?.link\n        if (deepLink != null) {\n            navigateToContent(deepLink)\n        }\n    }\n<\/code><\/pre>\n\n\n\n
With Dynamic Links shut down, this code no longer works.<\/p>\n\n\n\n
What Replaced Firebase App Indexing<\/h2>\n\n\n\n
Google did not provide a direct 1:1 replacement. Instead, the functionality is split across several systems:<\/p>\n\n\n\n
Android App Links (Replaces Deep Link Handling)<\/h3>\n\n\n\n
Android App Links<\/a> are the standard way to handle HTTPS deep links on Android. They existed before Firebase App Indexing and continue to work independently:<\/p>\n\n\n\n
<intent-filter android:autoVerify="true">\n    <action android:name="android.intent.action.VIEW" \/>\n    <category android:name="android.intent.category.DEFAULT" \/>\n    <category android:name="android.intent.category.BROWSABLE" \/>\n    <data android:scheme="https"\n          android:host="www.yourapp.com"\n          android:pathPrefix="\/products" \/>\n<\/intent-filter>\n<\/code><\/pre>\n\n\n\n
App Links require hosting a Digital Asset Links<\/a> file (assetlinks.json<\/code>) on your domain.<\/p>\n\n\n\n
Web Markup + Search Console (Replaces App Indexing API)<\/h3>\n\n\n\n
The App Indexing API's function (telling Google about in-app content) is now handled by web-side markup:<\/p>\n\n\n\n
    \n
  1. Structured data<\/strong> on your web pages declares that app alternatives exist.<\/li>\n
  2. Alternate link tags<\/strong> point to your Android app.<\/li>\n
  3. Search Console<\/strong> verifies the web-app connection.<\/li>\n<\/ol>\n\n\n\n
    <!-- Web page markup that replaces App Indexing API -->\n<link rel="alternate" href="android-app:\/\/com.yourapp.android\/https\/www.yourapp.com\/products\/123" \/>\n<\/code><\/pre>\n\n\n\n
    See Google App Indexing setup<\/a> for the full implementation.<\/p>\n\n\n\n
    Third-Party Deep Linking Platforms (Replaces Dynamic Links)<\/h3>\n\n\n\n
    For the deep link creation, routing, and analytics that Firebase Dynamic Links provided, third-party platforms fill the gap. Tolinku<\/a> handles the infrastructure: custom domains, verification file hosting, route configuration, and deep link analytics.<\/p>\n\n\n\n
    Migration Steps<\/h2>\n\n\n\n
    Step 1: Remove Firebase App Indexing SDK<\/h3>\n\n\n\n
    Remove the Firebase App Indexing dependency from your project:<\/p>\n\n\n\n
    \/\/ Remove from build.gradle\n\/\/ implementation 'com.google.firebase:firebase-appindexing:20.0.0'\n<\/code><\/pre>\n\n\n\n
    Remove all FirebaseAppIndex<\/code> and Indexable<\/code> code from your Activities.<\/p>\n\n\n\n
    Step 2: Set Up Android App Links<\/h3>\n\n\n\n
    If you were relying on Firebase Dynamic Links for deep link handling, switch to Android App Links:<\/p>\n\n\n\n
      \n
    1. Add intent filters to your AndroidManifest.xml<\/code> for each content type your app handles.<\/li>\n
    2. Host assetlinks.json<\/code> on your domain (or use a platform like Tolinku that hosts it automatically).<\/li>\n
    3. Handle incoming intents in your Activities.<\/li>\n<\/ol>\n\n\n\n
      class ProductActivity : AppCompatActivity() {\n    override fun onCreate(savedInstanceState: Bundle?) {\n        super.onCreate(savedInstanceState)\n\n        val uri = intent.data ?: return\n        val productId = uri.lastPathSegment ?: return\n        loadProduct(productId)\n    }\n}\n<\/code><\/pre>\n\n\n\n
      Step 3: Add Web Markup<\/h3>\n\n\n\n
      Replace the App Indexing API's content reporting with web-side markup:<\/p>\n\n\n\n
        \n
      1. Add <link rel="alternate"><\/code> tags to your web pages.<\/li>\n
      2. Add structured data with potentialAction<\/code> for richer results.<\/li>\n
      3. Submit your sitemap to Search Console with app link annotations.<\/li>\n<\/ol>\n\n\n\n
        <head>\n  <link rel="alternate" href="android-app:\/\/com.yourapp.android\/https\/www.yourapp.com\/products\/123" \/>\n<\/head>\n<\/code><\/pre>\n\n\n\n
        Step 4: Verify in Search Console<\/h3>\n\n\n\n
          \n
        1. Open Google Search Console<\/a>.<\/li>\n
        2. Go to Settings > Associations.<\/li>\n
        3. Link your Android app.<\/li>\n
        4. Use the URL Inspection tool to verify that app link annotations are detected.<\/li>\n<\/ol>\n\n\n\n
          Step 5: Monitor App Search Traffic<\/h3>\n\n\n\n
          After migration, monitor your app's search performance:<\/p>\n\n\n\n